On 12/2/06, Wit <[EMAIL PROTECTED]> wrote:
Dan Nicholson wrote:
> On 12/2/06, Wit <[EMAIL PROTECTED]> wrote:
>> Dan Nicholson wrote:
>> <snip>
> Configure seems to cache the prefix value. When you rerun
> configure.gnu, --prefix= doesn't seem to change anything. I meant to
> check whether -Dprefix= (the real option used in Configure) would
> help, but perl's ugliness stopped me considerably.
Maybe something has changed for the better? I ran pearl, readline, zlib
and autoconf over again and seem to have been OK (see my [SOLVED] post).
Do you want me to examine any of the logs/guess or what before I remove
the dirs?
Good. That should have worked once perl was reinstalled knowing the
right prefix of /usr.
How about some kind of test to ensure that autoconf is really OK now? I
just saw now "Error" entries in the log and saw install looked OK.
Run the testsuite?
> So, if you'd like to run Configure to get your defaults laid out, I
> think you'd want to remove the directory after that saving Policy.sh,
> which has the settings you made. Or something like that. Or running
> Configure directly with:
>
> sh Configure -des -Dprefix=/usr ...
>
> That's essentially what configure.gnu is doing. -Dprefix might not
> have any effect though if prefix already is set to /usr/local.
What can I look for to see if I need to do this? I can upload files from
that machine to this over my network (I *think* - haven't tried that
yet) and post.
You shouldn't have to. If you freshly unpacked perl and just run
configure.gnu with --prefix=/usr, it will get it right.
Here's the issue. You run Configure once to see what settings you
want. It caches these settings in config.sh and Policy.sh. The next
time you run Configure (through configure.gnu), it just uses what's in
config.sh and does not use the new settings you passed.
But now I have this bastard figured out. If you just remove config.sh
and Policy.sh, it will not try to use any cached values. Or you can
run Configure directly with the -O setting.
The whole note is a bad idea because there's no reasonable way to find
the settings you want then run Configure for real. I suppose the only
real way to do it is to run configure.gnu like is said in the book,
then run Configure interactively and change any settings you don't
like. Then the locations will be cached to the right values for LFS.
Hmm, maybe that's the solution.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
