• 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: Linking conflicts with new Foundation from Safari 1.0
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linking conflicts with new Foundation from Safari 1.0


  • Subject: Re: Linking conflicts with new Foundation from Safari 1.0
  • From: Chris Kane <email@hidden>
  • Date: Fri, 25 Jul 2003 10:51:34 -0700

This is a bug in the Safari 1.0 goodies (specifically the new version of Foundation framework inside the package), in that a symbol named _fields should not be being exported. Panther won't have this problem, but there's little you can do about it on 10.2.6. If you don't use the symbol _fields from the .a library, there may be a way to use the 'nmedit' command to 'remove' the symbol, though I don't know if that works on .a files. The strip command might be another possibility.


Chris Kane
Cocoa Frameworks, Apple


On Tuesday, July 8, 2003, at 20:47, Michael McCracken wrote:

(Apologies for the re-post from macosx-dev, it seems like there's more people here.)

I've had a frustrating problem with a fatal linking error that has cropped up since I've installed Safari 1.0, and I'd appreciate any help I can get. Here's the situation:

I use a library (not a framework) that defines the symbol "_fields" - which was never a problem until June 23. After installing Safari 1.0 (which installs a new Foundation at /System/Library/Frameworks/Foundation.framework/Versions/C), my application fails to build, with the following errors:

ld: multiple definitions of symbol _fields
/System/Library/Frameworks/Foundation.framework/Versions/C/
Foundation(ProjectBuilderMasterObjectFile.o) definition of _fields
./libbtparse.a(bibtex.o) definition of _fields in section (__TEXT,__text)

My initial response was to go try to edit bibtex.c and just rename the symbol to avoid the collision. However, that's a generated parser (made by PCCTS) and it isn't that simple to just change it. Although I probably can figure out how eventually, I was wondering if anyone knows of a better solution? It really seems like I shouldn't have to change my code here.

Thanks,
-Michael
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Linking conflicts with new Foundation from Safari 1.0 (From: Michael McCracken <email@hidden>)

  • Prev by Date: Re: FoundationKit md5/checksum
  • Next by Date: Re: working with font manager
  • Previous by thread: Linking conflicts with new Foundation from Safari 1.0
  • Next by thread: Re: Duplicating Apple search field UI
  • Index(es):
    • Date
    • Thread