Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / CodeWarrior / December 2004



Tip: Looking for answers? Try searching our database.

Problem linking new Shockwave libs into Mach-O target

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Northern Lights Info - 18 Dec 2004 17:36 GMT
Macromedia has posted new Shockwave libraries for Mach-O targets.  However,
linking them into a CW 9.3 Mach-O project gives the following error:

Internal Mach-O Importer Error File "ImportMachO.c" Line 580 unexpected
ar_fmag

Any ideas?

Blair M. Burtan
Northern Lights Productions
http://www.northernlights3D.com
Northern Lights Info - 18 Dec 2004 19:46 GMT
Disregard the post about the Shockwave libraries.  Tried to link the Windows
versions.  Oops.

I'm now getting a link error that appears to be OpenGL-related.
"dyld_stub_binding_helper is undefined used by '_glReadBuffer'"

Ideas?

Blair M. Burtan
Northern Lights Productions
http://www.northernlights3D.com
Jesper Madsen - 19 Dec 2004 16:55 GMT
crt1.0 needs to be linked think
> Disregard the post about the Shockwave libraries.  Tried to link the Windows
> versions.  Oops.
[quoted text clipped - 7 lines]
> Northern Lights Productions
> http://www.northernlights3D.com
Jesper Madsen - 29 Dec 2004 17:38 GMT
> crt1.0 needs to be linked think
> > Disregard the post about the Shockwave libraries.  Tried to link the
[quoted text clipped - 9 lines]
> > Northern Lights Productions
> > http://www.northernlights3D.com

That came out wrong... Should have said "I think" instead of think...
Eric VERGNAUD - 19 Dec 2004 11:38 GMT
Hi,

I have a project which links with various static libraries compiled with
gcc. I'm encountering memory problems which result from the following
typical scenario:

- the library calls strdup. Because it's linked with MSL, it calls MSL's
strdup, which in turns calls _sys_malloc instead of malloc.
- the library tries to free the memory alloced by strdup. Since I'm also
linking with the system framework, malloc is called, and MallocDeug
complains that it's trying to free an unallocated pointer

In one of the libraries, I managed to replace the strdup calls by a custom
strdup which calls malloc, and that fixed the problem. However, due to the
number of static gcc libraries I'm linking with, I expect this problem to
arise again.

Is there a way I can compile MSL so that it uses the system's malloc instead
of it's own scheme ?

Eric
Miro Jurisic - 19 Dec 2004 12:51 GMT
> Is there a way I can compile MSL so that it uses the system's malloc instead
> of it's own scheme ?

See _MSL_OS_DIRECT_MALLOC in ansi_prefix.mac.h

hth

meeroh

Signature

If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.