Hi Peter,
* Peter O'Gorman wrote on Thu, Jan 31, 2008 at 08:00:59AM CET:
I installed amd64 debian in a VM and with this patch I get:
/usr/lib/gcc/x86_64-linux/gnu/4.1.2 /usr/lib /lib
I do not know if it is best to leave in the symlink and the original dir
( i.e. do cd $dir pwd as well as
Ralf Wildenhues wrote:
I have not yet tried to understand the logic of the patch.
Sorry. I have dropped it. libstdc++ should still be found because of the
compiler_search_path changes.
Peter
--
Peter O'Gorman
http://pogma.com
Not much response last time, here we go again.
Libtool, for compilers other than gcc, does not usually care about the
compiler's internal search paths, and if it does, it is not very likely
to find .la files in there. In the case of gcc, libtool insists on
knowing the compilers internal search
Hi Peter,
* Peter O'Gorman wrote on Wed, Jan 30, 2008 at 09:16:38AM CET:
Not much response last time, here we go again.
Sorry about the delay.
Ok to apply to branch-1-5 and forward port to HEAD?
Nits below.
FWIW, on Debian x86_64, this patch causes for me /usr/lib to appear
in the front,
Ralf Wildenhues wrote:
Hi Peter,
* Peter O'Gorman wrote on Wed, Jan 30, 2008 at 09:16:38AM CET:
Not much response last time, here we go again.
Sorry about the delay.
Ok to apply to branch-1-5 and forward port to HEAD?
Nits below.
FWIW, on Debian x86_64, this patch causes for me
* Peter O'Gorman wrote on Thu, Jan 31, 2008 at 08:00:59AM CET:
I do not know if it is best to leave in the symlink and the original dir
( i.e. do cd $dir pwd as well as cd $dir pwd -P), which on debian
would give something like:
/usr/lib/gcc/x86_64-linux/gnu/4.1.2 /usr/lib64 /usr/lib /lib64
