On Wed, 1 Sep 2010 20:24:19 +0100, Ken Moffat
wrote:
> On 1 September 2010 14:41, Matthew Burgess
> wrote:
>
>> I lied before [0] and I do see this. Why are we using
> 'LD_LIBRARY_PATH' instead
>> of --disable-libgomp in pass2 as we do in pass 1? (yes, I'm well aware
> that it was
>> me that c
On 1 September 2010 14:41, Matthew Burgess wrote:
> I lied before [0] and I do see this. Why are we using 'LD_LIBRARY_PATH'
> instead
> of --disable-libgomp in pass2 as we do in pass 1? (yes, I'm well aware that
> it was
> me that committed r9254 that added this as part of the upgrade to GCC-4
On Wed, 4 Aug 2010 23:56:41 +0100, Ken Moffat
wrote:
> Actually, this is the first problem I saw, but I've waited until the final
> toolchain was completed before I mention it.
>
> On x86_64, with glibc-2.12.1 and otherwise the 20100803 book, in
> pass 2 glibc the build failed in libgomp with
>
On 8/4/10 6:56 PM, Ken Moffat wrote:
> Actually, this is the first problem I saw, but I've waited until the final
> toolchain was completed before I mention it.
>
> On x86_64, with glibc-2.12.1 and otherwise the 20100803 book, in
> pass 2 glibc the build failed in libgomp with
>
> configure: error:
On Wed, 4 Aug 2010 23:56:41 +0100, Ken Moffat
wrote:
>
> On x86_64, with glibc-2.12.1 and otherwise the 20100803 book, in
> pass 2 glibc the build failed in libgomp with
>
> configure: error: unsupported system, cannot find sizeof (omp_lock_t)
> make[1]: *** [configure-target-libgomp] Error 1
>
Actually, this is the first problem I saw, but I've waited until the final
toolchain was completed before I mention it.
On x86_64, with glibc-2.12.1 and otherwise the 20100803 book, in
pass 2 glibc the build failed in libgomp with
configure: error: unsupported system, cannot find sizeof (omp_lock
