public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Eager <eager@mvista.com>
To: gcc-help@gcc.gnu.org
Subject: Error building cross-gcc libgcc_s.so
Date: Thu, 28 Dec 2000 15:00:00 -0000	[thread overview]
Message-ID: <3A4BC4FD.7FF62667@mvista.com> (raw)

I'm getting an error while building cross-GCC for i586 with newlib.  I'm
using the current CVS mainline.

My configuration (cross x86 compiler):
./Source/gcc/configure --with-gcc-version-trigger=./Source/gcc/gcc/version.c
  --host=i686-pc-linux-gnu --prefix=./Install --target=i586-hardhat-linux
  --program-prefix=i586- --enable-cross --enable-languages=c
  --with-headers=/opt/hardhat/devkit/i586-hardhat-linux/include --with-newlib
  --norecursion     

The error occurs while trying to build a shared library version of libgcc_s.so:

./Build/GCC-i586-hardhat-linux-20001228/gcc/xgcc
  -B./Build/GCC-i586-hardhat-linux-20001228/gcc/
  -B./Install/i586-hardhat-linux/bin/
  -B./Install/i586-hardhat-linux/lib/ -isystem 
  ./Install/i586-hardhat-linux/include -O2  -DCROSS_COMPILE -DIN_GCC
  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem
  ./include  -fPIC -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc 
  -shared -nodefaultlibs -Wl,--soname=libgcc_s.so.0 -Wl,--version-script=libgcc.map
  -o libgcc_s.so   libgcc/./_muldi3.o libgcc/./_divdi3.o libgcc/./_moddi3.o 
  <lotsa object files>
  -lc                              
./Install/i586-hardhat-linux/bin/ld: cannot open crti.o: No such file or directory 

The specs file contains the following:

	*startfile:
	%{!shared: %{pg:gcrt1.o%s} %{!pg:%{p:gcrt1.o%s}
        %{!p:%{profile:gcrt1.o%s} %{!profile:crt1.o%s}}}}    
	crti.o%s %{!shared:crtbegin.o%s} %{shared:crtbeginS.o%s} 

	*endfile:
	%{!shared:crtend.o%s} %{shared:crtendS.o%s} crtn.o%s    

Since crti.o (or crtn.o) isn't built in the current directory, the 
linker cannot find it. 

Why should crti.o and crtn.o be included in a shared library?
Or in libgcc?

Why is libc also linked in with libgcc?  Since newlib hasn't been
built, there isn't one to link with.

Is there something that I'm doing wrong?

--

Michael Eager
Senior Tools Developer	  Phone: (408) 328-8426
MontaVista Software, Inc.   Fax: (408) 328-9204
1237 E. Arques Avenue	    Web: www.hardhatlinux.com
Sunnyvale, CA 94085	  Email: eager@mvista.com

             reply	other threads:[~2000-12-28 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-28 15:00 Michael Eager [this message]
2000-12-28 19:40 ` Alexandre Oliva

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A4BC4FD.7FF62667@mvista.com \
    --to=eager@mvista.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).