crt[i1].o with multiarch glibc

crt[i1].o with multiarch glibc

[Michael Welsh Duggan]

The Debian GNU/Linux distribution (and Ubuntu, it appears) have been
working on multiarch support in its unstable distribution.  (See
http://wiki.debian.org/Multiarch/ for details.)  This means that crt1.o
and crti.o end up in /usr/lib/i386-linux-gnu instead of /usr/lib.  Once
I figured this out, I was able to use --with-crt-dir to allow things to
compile again.

I was going to suggest that configure.in checked for the proper files in
/usr/lib/${canonical}, but ${canonical} is i686-pc-linux-gnu on this
system, so some reduction would have to be done to make that work.  If
this cannot or will not be done, it would be nice to add this to the
PROBLEMS file.

I would volunteer to do either of these, but I've had difficulty getting
an employer disclaimer.

-- 
Michael Welsh Duggan
(md5i@md5i.com)

Re: crt[i1].o with multiarch glibc

[Andreas Schwab]

Michael Welsh Duggan <md5i@md5i.com> writes:

> I was going to suggest that configure.in checked for the proper files in
> /usr/lib/${canonical}, but ${canonical} is i686-pc-linux-gnu on this
> system, so some reduction would have to be done to make that work.  If
> this cannot or will not be done, it would be nice to add this to the
> PROBLEMS file.

Does `gcc -print-file-name=crt1.o' work?

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: crt[i1].o with multiarch glibc

[Michael Welsh Duggan]

Andreas Schwab <schwab@linux-m68k.org> writes:

> Michael Welsh Duggan <md5i@md5i.com> writes:
>
>> I was going to suggest that configure.in checked for the proper files in
>> /usr/lib/${canonical}, but ${canonical} is i686-pc-linux-gnu on this
>> system, so some reduction would have to be done to make that work.  If
>> this cannot or will not be done, it would be nice to add this to the
>> PROBLEMS file.
>
> Does `gcc -print-file-name=crt1.o' work?

It does:

md5i@maru:~$ gcc -print-file-name=crt1.o
/usr/lib/i386-linux-gnu/gcc/i486-linux-gnu/4.6.1/../../../crt1.o

-- 
Michael Welsh Duggan
(md5i@md5i.com)

Re: crt[i1].o with multiarch glibc

[David De La Harpe Golden]

On 03/07/11 20:02, Michael Welsh Duggan wrote:
> Andreas Schwab<schwab@linux-m68k.org>  writes:

>> Does `gcc -print-file-name=crt1.o' work?
>
> It does:
>
> md5i@maru:~$ gcc -print-file-name=crt1.o
> /usr/lib/i386-linux-gnu/gcc/i486-linux-gnu/4.6.1/../../../crt1.o
>

But note that Glenn Morris recently (trunk rev 104778+) added a hack to 
configure.in to use -print-file-name to find the files. Is it not 
working on your system?

Re: crt[i1].o with multiarch glibc

[Michael Welsh Duggan]

David De La Harpe Golden <david@harpegolden.net> writes:

> On 03/07/11 20:02, Michael Welsh Duggan wrote:
>> Andreas Schwab<schwab@linux-m68k.org>  writes:
>
>>> Does `gcc -print-file-name=crt1.o' work?
>>
>> It does:
>>
>> md5i@maru:~$ gcc -print-file-name=crt1.o
>> /usr/lib/i386-linux-gnu/gcc/i486-linux-gnu/4.6.1/../../../crt1.o
>>
>
> But note that Glenn Morris recently (trunk rev 104778+) added a hack
> to configure.in to use -print-file-name to find the files. Is it not
> working on your system?

Cancel that.  It was my fault, building in a different tree than the one
I had updated.  My apologies.  I can confirm that this works for me.

-- 
Michael Welsh Duggan
(md5i@md5i.com)