• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Interesting problem with Xcode 3.0
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Interesting problem with Xcode 3.0


  • Subject: Re: Interesting problem with Xcode 3.0
  • From: Jean-Daniel Dupas <email@hidden>
  • Date: Fri, 15 Feb 2008 15:02:44 +0100


Le 15 févr. 08 à 14:27, Richard Bannister a écrit :

Folks

One of my projects has a a small snippet of x86 assembly in it.

In order to make this code compile correctly I need to use -static and -fomit-frame-pointer on the command line. In other words, I can build it like this:

	gcc -static -fomit-frame-pointer file.c -o file.o

I'm trying to get it to build in my Xcode project with these options.. I've added the two flags to the Build tab of the file info:

	-static -fomit-frame-pointer

Unfortunately, it will not compile, throwing the following error:

{standard input}:2:FATAL:incompatible feature used: section type symbol_stubs (must specify "-dynamic" to be used)

Can anyone advise how I might work around this?

Many thanks,

Richard

Why do you need to use -static ?

According to gcc manpage:
This option will not work on Mac OS X unless all libraries (including libgcc.a) have also been compiled with -static.
Since neither a static version of libSystem.dylib nor crt0.o are provided, this option is not useful to most people.


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Interesting problem with Xcode 3.0
      • From: Richard Bannister <email@hidden>
References: 
 >Interesting problem with Xcode 3.0 (From: Richard Bannister <email@hidden>)

  • Prev by Date: Interesting problem with Xcode 3.0
  • Next by Date: Re: Interesting problem with Xcode 3.0
  • Previous by thread: Interesting problem with Xcode 3.0
  • Next by thread: Re: Interesting problem with Xcode 3.0
  • Index(es):
    • Date
    • Thread