www.digitalmars.com         C & C++   DMDScript  

D.gnu - GDC Build Failing

reply Steve Teale <steve.teale britseyeview.com> writes:
I'm having a failure compiling libgcc2.c - fatal error: gnu/stubs-32.h: 
No such file or directory.

I got round that by copying the file from /usr/include/i386-linux-gnu/gnu 
intp /usr/include/gnu.

Then the build goes on, but later I get get:

checking dynamic linker characteristics... configure: error: Link tests 
are not allowed after GCC_NO_EXECUTABLES.

Any suggestions?

Steve
Feb 06 2012
next sibling parent Trass3r <un known.com> writes:
Which distro?
Feb 06 2012
prev sibling next sibling parent Iain Buclaw <ibuclaw ubuntu.com> writes:
On 6 February 2012 12:50, Steve Teale <steve.teale britseyeview.com> wrote:
 I'm having a failure compiling libgcc2.c - fatal error: gnu/stubs-32.h:
 No such file or directory.

 I got round that by copying the file from /usr/include/i386-linux-gnu/gnu
 intp /usr/include/gnu.

 Then the build goes on, but later I get get:

 checking dynamic linker characteristics... configure: error: Link tests
 are not allowed after GCC_NO_EXECUTABLES.

 Any suggestions?

 Steve

Looks like you don't have 32bit headers installed on your machine. If you can't obtain them, build with --disable-multilib. Regards. -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';
Feb 06 2012
prev sibling next sibling parent Steve Teale <steve.teale britseyeview.com> writes:
On Mon, 06 Feb 2012 13:17:00 +0000, Iain Buclaw wrote:

 On 6 February 2012 12:50, Steve Teale <steve.teale britseyeview.com>
 wrote:
 I'm having a failure compiling libgcc2.c - fatal error: gnu/stubs-32.h:
 No such file or directory.

 I got round that by copying the file from
 /usr/include/i386-linux-gnu/gnu intp /usr/include/gnu.

 Then the build goes on, but later I get get:

 checking dynamic linker characteristics... configure: error: Link tests
 are not allowed after GCC_NO_EXECUTABLES.

 Any suggestions?

 Steve

Looks like you don't have 32bit headers installed on your machine. If you can't obtain them, build with --disable-multilib.

OK, perhaps a pertinent question is what is the default build? I have 32 bit Ubuntu installed on a 64 bit two core machine. The header in question is there and specifically under i396-gnu, so I have some 32 bit headers. Would it not complain about others? Steve
 
 
 Regards.

Feb 06 2012
prev sibling next sibling parent Iain Buclaw <ibuclaw ubuntu.com> writes:
On 6 February 2012 16:14, Steve Teale <steve.teale britseyeview.com> wrote:
 On Mon, 06 Feb 2012 13:17:00 +0000, Iain Buclaw wrote:

 On 6 February 2012 12:50, Steve Teale <steve.teale britseyeview.com>
 wrote:
 I'm having a failure compiling libgcc2.c - fatal error: gnu/stubs-32.h:
 No such file or directory.

 I got round that by copying the file from
 /usr/include/i386-linux-gnu/gnu intp /usr/include/gnu.

 Then the build goes on, but later I get get:

 checking dynamic linker characteristics... configure: error: Link tests
 are not allowed after GCC_NO_EXECUTABLES.

 Any suggestions?

 Steve

Looks like you don't have 32bit headers installed on your machine. =A0If you can't obtain them, build with --disable-multilib.

OK, perhaps a pertinent question is what is the default build? I have 32 bit Ubuntu installed on a 64 bit two core machine. The header in question is there and specifically under i396-gnu, so I have some 32 bit headers. Would it not complain about others? Steve
 Regards.


For Ubuntu and Debian, being that i386 and x86_64 (possibly others) are multi-arch systems, you may need to set-up LIBRARY_PATH and CPATH. In ~/.bashrc: LIBRARY_PATH=3D/usr/lib/i386-linux-gnu CPATH=3D/usr/include/i386-linux-gnu export LIBRARY_PATH CPATH I have said this at least a dozen times, this must be documented somewhere.= .. :) --=20 Iain Buclaw *(p < e ? p++ : p) =3D (c & 0x0f) + '0';
Feb 06 2012
prev sibling parent Steve Teale <steve.teale britseyeview.com> writes:
On Mon, 06 Feb 2012 16:31:40 +0000, Iain Buclaw wrote:


multi-arch systems, you may need to set-up LIBRARY_PATH and CPATH. In ~/.bashrc: LIBRARY_PATH=/usr/lib/i386-linux-gnu CPATH=/usr/include/i386-linux-gnu export LIBRARY_PATH CPATH I have said this at least a dozen times, this must be documented somewhere... :)

That does the trick, but to avoid confusion, if you have already got into trouble it is best to remove objdir, close your terminal window, and start again from the point where objdir is created. Thanks ever so Steve
Feb 06 2012