• 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 Errors for all vecLib.h calls
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linking Errors for all vecLib.h calls

  • Subject: Re: Linking Errors for all vecLib.h calls
  • From: dct <email@hidden>
  • Date: Tue, 29 Apr 2008 12:30:33 -0700
Jean Daniel

Merci, merci.  It worked.

I added the OSX 10.5 version of Accelerate.framework by selecting "Other Frameworks" under Groups & Files then did Project > Add to Project and navigating to Accelerate.framework.

I am at a loss to understand why this had to be done for Xcode 3.0 given that 2.4.1 ran just fine without the Accelerate framework being explicitly added at the Groups & Files level.

Thanks again for your help.  Don


On Apr 29, 2008, at 11:42 AM, Jean-Daniel Dupas wrote:


And now, we can say that the problem is simply because you do not actually link to the Accelerated framework. (you don't tell the linker to use it)
You have to add the framework to your project and if it is already here, you have to add it to your target. 
You can either drop it in the «Targets > "your target" > Link Binary With Libraries» build phase, or select the framework in Xcode, open information panel (cmd + i), choose the Target tab, and check the box corresponding to your target.



Le 29 avr. 08 à 20:33, dct a écrit :

Here is the information associated with the Linking error statement:
"Linking /User/Shared/Data Files/Development ƒ/Cocoa/Cafe/build/Development/Cafe.app/Contents/MaxOS/Cafe (97 errors)" --

    cd "/Users/Shared/Data Files/Development ƒ/Cocoa/Cafe"
    /Developer/usr/bin/gcc-4.0 -o "/Users/Shared/Data Files/Development ƒ/Cocoa/Cafe/build/Development/Cafe.app/Contents/MacOS/Cafe" "-L/Users/Shared/Data Files/Development ƒ/Cocoa/Cafe/build/Development" "-F/Users/Shared/Data Files/Development ƒ/Cocoa/Cafe/build/Development" -filelist "/Users/Shared/Data Files/Development ƒ/Cocoa/Cafe/build/Cafe.build/Development/Cafe (Upgraded) 2.build/Objects-normal/i386/Cafe.LinkFileList" -framework Cocoa -arch i386 -prebind -mmacosx-version-min=10.5 -isysroot /Developer/SDKs/MacOSX10.5.sdk
Undefined symbols:
  "_vDSP_vqint", referenced from:
      _vQuadInterpolate in DSP_vOperations.o
      _vQuadInterpolate in DSP_vOperations.o
  "_vDSP_vsbsm", referenced from:
      _rDerivative in DSP_vOperationsII.o
  "_vDSP_vtabi", referenced from:
      _rTableLU in DSP_vOperationsII.o
..... (for 94 more)
ld: symbol(s) not found
collect2: ld returned 1 exit status


On Apr 29, 2008, at 12:32 AM, Jean-Daniel Dupas wrote:


Le 29 avr. 08 à 00:32, dct a écrit :

Added info:

The problem appears to be isolated to linking the Accelerate.framework.

The project, which includes a fair number of vDSP calls, compiles successfully (and I can force compile errors by making improper vDSP calls).  Obviously the compiler has access to the vecLib.framework via Accelerate.framework.

Unfortunately, once compiled, the project fails to link with the same Linking error statement (97 errors) cited in my first post.  It would appear that the linker can't find the framework that was accessed by the compiler (or am I missing something).

These results remain the same whether the Project Setting for "Cross-Develop Using Target SDK:" is set for "Mac OS X 10.5", "Mac OS X 10.4 (Universal)", or "Current Mac OS".

As a check, I built an old, prototype project that was last built about three years ago (and which has no vDSP calls); it built and ran perfectly.  I then added one vDSP call (with an #import <Accelerate/Accelerate.h> statement  in the appropriate header file).  As with my current project it compiled but failed to link.

Initial post:
"My current project fails to build with OSX 10.5.2 and Xcode 3.0 with a Linking error statement:
"Linking/Users/.../MacOS/Cafe (97 errors)
"_vDSP_vquint"' referenced from: ...
"_vDSP_vsbsm"' referenced from: ...
etc (for 97 separate calls) "
Obviously the linker can't find the framework <Accelerate/Accelerate.h>.

This  same project builds without error on a MacMini still configured with OSX 10.4.11 & Xcode 2.4.1.

A Spotlight search for "Accelerate.h" reveals three separate paths:
-- /Developer/SDKs/MacOSX10.4u.sdk/.../Accelerate.framework/.../Headers
-- /Developer/SDKs/MacOSX10.5.sdk/.../Accelerate.framework/.../Headers
-- /System/Library/Frameworks/Accelerate.framework/.../Headers.
A search for "vecLib.h" reveals four separate paths:
-- /Developer/SDKs/MacOSX10.4u.sdk/.../vecLib.framework/.../Headers
-- /Developer/SDKs/MacOSX10.4u.sdk/.../Accelerate.framework/.../vecLib.framework/.../Headers
-- /Developer/SDKs/MacOSX10.5.sdk/.../vecLib.framework/.../Headers
-- /Developer/SDKs/MacOSX10.5.sdk/.../Accelerate.framework/.../vecLib.framework/.../Headers
(I have no idea whether this has anything to do with my problem.)

Any suggestions?  I'm stumped and need help."

Yes, posts the linker invocation command line (transcript) instead of just posting the error. We should be able to find what goes wrong from it.





 _______________________________________________
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
References: 
 >Re:Linking Errors for all vecLib.h calls (From: dct <email@hidden>)
 >Re: Linking Errors for all vecLib.h calls (From: Jean-Daniel Dupas <email@hidden>)
 >Re: Linking Errors for all vecLib.h calls (From: dct <email@hidden>)
 >Re: Linking Errors for all vecLib.h calls (From: Jean-Daniel Dupas <email@hidden>)

  • Prev by Date: Re: Xcode 3 losing scm password
  • Next by Date: Re: What is a project?
  • Previous by thread: Re: Linking Errors for all vecLib.h calls
  • Next by thread: Debugger doesn't stop (most of the time)
  • Index(es):
    • Date
    • Thread