This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RS6000: Missing EABI symbols at link time

From: Nick Clifton <nickc at redhat dot com>
To: David Edelsohn <dje at watson dot ibm dot com>
Cc: geoffk at geoffk dot org, amodra at bigpond dot net dot au, gcc-patches at gcc dot gnu dot org
Date: Fri, 03 Feb 2006 12:34:57 +0000
Subject: Re: RS6000: Missing EABI symbols at link time
References: <m3hd7j3yjj.fsf@redhat.com> <200602011547.k11FlbD29608@makai.watson.ibm.com>

Hi David,

	All of the powerpc-eabi configurations include freebsd-spec.h and
rs6000/freebsd.h, which set the rs6000/sysv4.h SPEC to FreeBSD versions.

True - but this spec is only used when -mcall-freebsd is enabled on the command line. My problem is that the default multilib selection has an empty startfile spec (and endfile spec) and so the compiler, by default, cannot link a working executable.

Is crti.o being provided somewhere?

No.

I think that crti.o should be
providing those references without adding ecrti.o to the startfile spec.

OK - so who or what should be providing crti.o ?

Plus this still leaves the problem that currently the default startfile spec is empty so no crt?.o files are being placed on the linker's command line.o. Maybe the problem is in config/rs6000/sysv4.h where it defines the empty STARTFILE_DEFAULT_SPEC ? Perhaps this should be changed to be "crti.o%s" ?

Cheers
  Nick

Follow-Ups:
- Re: RS6000: Missing EABI symbols at link time
  - From: David Edelsohn

References:
- RS6000: Missing EABI symbols at link time
  - From: Nick Clifton
- Re: RS6000: Missing EABI symbols at link time
  - From: David Edelsohn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]