Gcc testsuite, LD_LIBRARY_PATH, and a new libgcc_s that is incompatible with the host libc

2012-06-22 Thread Simon Baldwin
I've recently encountered a gcc testsuite issue that is caused by the libgcc_s in the built compiler being incompatible with, but the same architecture as, the host's libc. I'm not sure what the right fix is, so I'm looking for ideas. I build gcc-4.7 for x86 on an x86 host. The bootstrap

Re: Gcc testsuite, LD_LIBRARY_PATH, and a new libgcc_s that is incompatible with the host libc

2012-06-22 Thread Andrew Haley
On 06/22/2012 11:35 AM, Simon Baldwin wrote: Firstly, has anyone else encountered this or otherwise given it any thought? And secondly, any hints for practical fixes? What you effectively seem to be building is a cross-compiler from x86-glibc-A to x86-glibc-B. To run your tests, you want a

Re: Gcc testsuite, LD_LIBRARY_PATH, and a new libgcc_s that is incompatible with the host libc

2012-06-22 Thread Ian Lance Taylor
Andrew Haley a...@redhat.com writes: On 06/22/2012 11:35 AM, Simon Baldwin wrote: Firstly, has anyone else encountered this or otherwise given it any thought? And secondly, any hints for practical fixes? What you effectively seem to be building is a cross-compiler from x86-glibc-A to

Re: Gcc testsuite, LD_LIBRARY_PATH, and a new libgcc_s that is incompatible with the host libc

2012-06-22 Thread Andrew Haley
On 06/22/2012 03:27 PM, Ian Lance Taylor wrote: Andrew Haley a...@redhat.com writes: On 06/22/2012 11:35 AM, Simon Baldwin wrote: Firstly, has anyone else encountered this or otherwise given it any thought? And secondly, any hints for practical fixes? What you effectively seem to be

Re: Gcc testsuite, LD_LIBRARY_PATH, and a new libgcc_s that is incompatible with the host libc

2012-06-22 Thread Ian Lance Taylor
Andrew Haley a...@redhat.com writes: On 06/22/2012 03:27 PM, Ian Lance Taylor wrote: Andrew Haley a...@redhat.com writes: On 06/22/2012 11:35 AM, Simon Baldwin wrote: Firstly, has anyone else encountered this or otherwise given it any thought? And secondly, any hints for practical fixes?