Re: Partial autoconf transition thoughts

Alexandre Oliva
2003-06-13T19:25:40Z

On Jun 13, 2003, "Maciej W. Rozycki" <macro@ds2.pg.gda.pl> wrote:

> OK, the first is a native one, so it goes to $exec_prefix, say:
> /usr/lib. The second one is a cross one, so it goes to
> $exec_prefix/$target_alias, say: /usr/mipsel-linux/lib. Finally, the last
> one is a cross one, too, so it goes to $exec_prefix/$target_alias, say:
> /usr/mipsel-linux/lib -- oops! -- the second one just got overwritten...

Two crosses to the same target, and you don't want one to overwrite
the other? Well, then... I guess you want to add build timestamps
somewhere in the pathname or something.

More likely, I just misunderstand the scenario you have in mind :-)

>> Anyway, after re-reading the thread, I remember why we chose to do it
>> the way we did it. It does make sense, even thought I still find it
>> not ideal.

> I am looking forward to seeing any proposals for improvements.

My proposal back then was $exec_prefix/x-$target_alias for
host-x-target libraries. libraries for the target (i.e., not
libraries for host applications to manipulate target binaries, but
rather libraries containing code that will run on the target) would
still be in $exec_prefix/$target_alias, where they're currently
installed, but there's no reason why we couldn't move them to say
$prefix/$target_alias (since they depend on target, and are totally
independent of host), and use $exec_prefix/$target_alias for
host-x-target binaries.

--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer