Jean-Luc Delatre (Kevembuangga) wrote:
> The default location of the makefile is such that it
clobbers the
> original jhalfs/Makefile
You are misunderstanding how to use the software. The
following works
well for a user with ALL sudo privs and that has a home
directory of
'/home/builduser':
$ mkdir /home/builduser/jhalfs-build
$ svn co svn://linuxfromscratch.org/ALFS/jhalfs/trunk
jhalfs-source
$ cd jhalfs-source
$ make
(Adjust the setting 'General Settings -> Build
Directory' to be
"/home/builduser/jhalfs-build")
$ cd /home/builduser/jhalfs-build
$ make
The final make above begins the build process and uses a
*different*
Makefile from the one in the source. As you can see, the
source and
build directories are meant to be separate.
Now, if you do in fact have any other suggestions as to how
the process
can be improved or streamlined, we'd be glad to hear them.
Also, some
explanation as to what you mean by our attempt to be
'clever' would be
appreciated.
As a complete aside, Manuel, I've gotten to the point of
actually hating
the progress bar, I believe. No offense meant. It's a good
attempt and I
can appreciate both why you wrote it and why it's written as
it is. But
in my experience it slows down the build times, especially
on older
hardware, and it doesn't really tell you much of anything.
On all my
builds I always truncate common/progress_bar.sh before
starting. I know
I mentioned attempting a C-based progress bar at some point,
but I
haven't gotten around to it yet. Would anyone care if we
made this bit
of code optional in the configuration?
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page
|
