Subject: Re: sysinst, menuc & msgc and DESTDIR builds
To: Hubert Feyrer <hubert.feyrer@informatik.fh-regensburg.de>
From: None <jchacon@genuity.net>
List: tech-install
Date: 10/23/2000 13:10:42
Oh I agree. (Try building a 1.5 system from a 1.4.2 install base.)

Someone should probably tackle this post 1.5

James

>
>On Mon, 23 Oct 2000 jchacon@genuity.net wrote:
>> I did exactly this when I converted from a.out -> elf
>> 
>> It can be painful to manage though as I found the set of tools required
>> to build grows quite large.
>
>You bet. I think it would still give a nice cross-compiler framework...
>Plus - the reason why I wanted this - if would work if you had old tools 
>installed in your syetem. Finding out what you need to update before you
>can do a clean 'make build' isn't fun either...
>
>
> - Hubert
>
>> 
>> James
>> 
>> >
>> >On Mon, 23 Oct 2000, Bill Sommerfeld wrote:
>> >
>> >> >  > It seems the old menuc and msgc files are picked up when doing a DESTDIR
>> >> >  > build. Any objections to compile the patch below?
>> >> > 
>> >> > Yes.  You can't run DESTDIR's menuc(1), because you might be
>> >> > cross-compiling.
>> >> 
>> >> A correct patch would build a special menuc, etc., for a DESTDIR build
>> >> out of the current source tree with *HOST* tools.  This would require
>> >> menuc to be built twice: one with host tools, one with target tools..
>> >
>> >Why single out menuc? What we should have, is a toolchain target that
>> >builds all the host tools and requisite libraries. If you don't want
>> >to sully your main tree, you could set DESTDIR to a tools area and
>> >then set LD_LIBRARY_PATH and PATH for the real (cross) DESTDIR build.
>> >
>> >
>> >Frederick
>> >
>> >
>> >
>> >
>> >
>> 
>
>-- 
>Hubert Feyrer <hubert.feyrer@informatik.fh-regensburg.de>
>
>
>
>
>