Strange Xcode problems
by Leo "kingDUCTtape" Altmann · in Torque Game Engine · 05/08/2004 (5:19 pm) · 41 replies
I have been working with torque for a few months now, and using Xcode I've never really had any problems. But now, for some reason, whenever I try to compile, it fails due to one error:
Undefined symbols: _vorbis_info_blocksize
Obviously this is some problem with the ogg code. But the weird part is that it says Location: pb:0. When I double-click it, it just opens the pb folder. I re-downloaded the entire head from CVS, and tried compiling it w/o any source changes, and it still gave me this error. Ideas?
EDIT: By the way, I'm running OS X 10.3.3, on an iBook G3 800MHz.
Undefined symbols: _vorbis_info_blocksize
Obviously this is some problem with the ogg code. But the weird part is that it says Location: pb:0. When I double-click it, it just opens the pb folder. I re-downloaded the entire head from CVS, and tried compiling it w/o any source changes, and it still gave me this error. Ideas?
EDIT: By the way, I'm running OS X 10.3.3, on an iBook G3 800MHz.
About the author
#22
Sorry you had problems with your comp. Cool beans that this isn't a Torque-OSX problem. I figured not, but it's usually best to assume the worst and investigate from there.
Thanks to you for being patient and providing adequate information on the problem you were experiencing. That is always much appreciated, no matter what the cause of the problem is.
05/18/2004 (8:17 pm)
No prob. Sorry you had problems with your comp. Cool beans that this isn't a Torque-OSX problem. I figured not, but it's usually best to assume the worst and investigate from there.
Thanks to you for being patient and providing adequate information on the problem you were experiencing. That is always much appreciated, no matter what the cause of the problem is.
#23
It's worked fine yesterday and now it doesn't compile anymore.
Reinstalling OSX will not be fun at all! :(
Here the listing of the directory /usr/local/lib/
Is this a clue:
www.darkhorizons-lore.com/forum_viewtopic.php?7.632
06/22/2004 (10:53 am)
I'm just getting this error too!ld: warning prebinding disabled because dependent library: /usr/local/lib/libogg.0.dylib is not prebound (...) ld: Undefined symbols: _vorbis_info_blocksize
It's worked fine yesterday and now it doesn't compile anymore.
Reinstalling OSX will not be fun at all! :(
Here the listing of the directory /usr/local/lib/
Ordinateur-de-Mathieu-Lopez:/usr/local/lib mathieu$ ls -la total 7272 drwxr-xr-x 32 root wheel 1088 21 Jun 18:08 . drwxr-xr-x 10 root wheel 340 7 Feb 20:59 .. -rwxr-xr-x 1 root staff 6148 15 May 22:30 .DS_Store drwxr-xr-x 3 root wheel 102 6 Feb 19:35 audio -rw-r--r-- 1 root staff 12212 15 May 21:56 libdl.a lrwxrwxrwx 1 root wheel 23 21 Jun 18:08 libdl.dylib -> ../../lib/libdl.0.dylib -rwxr-xr-x 1 root staff 356272 15 May 22:30 libmp3lame.0.0.0.dylib lrwxrwxrwx 1 root wheel 22 21 Jun 18:08 libmp3lame.0.dylib -> libmp3lame.0.0.0.dylib -rw-r--r-- 1 root staff 413064 15 May 22:30 libmp3lame.a lrwxrwxrwx 1 root wheel 22 21 Jun 18:08 libmp3lame.dylib -> libmp3lame.0.0.0.dylib -rwxr-xr-x 1 root staff 816 15 May 22:30 libmp3lame.la -rwxr-xr-x 1 root staff 45252 15 May 20:49 libogg.0.2.0.dylib lrwxrwxrwx 1 root wheel 18 21 Jun 18:08 libogg.0.dylib -> libogg.0.2.0.dylib -rw-r--r-- 1 root staff 43420 15 May 20:49 libogg.a lrwxrwxrwx 1 root wheel 18 21 Jun 18:08 libogg.dylib -> libogg.0.2.0.dylib -rwxr-xr-x 1 root staff 662 15 May 20:49 libogg.la -rwxr-xr-x 1 root staff 476020 15 May 20:49 libvorbis.0.0.1.dylib lrwxrwxrwx 1 root wheel 21 21 Jun 18:08 libvorbis.0.dylib -> libvorbis.0.0.1.dylib -rw-r--r-- 1 root staff 741976 15 May 20:49 libvorbis.a lrwxrwxrwx 1 root wheel 21 21 Jun 18:08 libvorbis.dylib -> libvorbis.0.0.1.dylib -rwxr-xr-x 1 root staff 697 15 May 20:49 libvorbis.la -rwxr-xr-x 1 root staff 643460 15 May 20:49 libvorbisenc.0.0.1.dylib lrwxrwxrwx 1 root wheel 24 21 Jun 18:08 libvorbisenc.0.dylib -> libvorbisenc.0.0.1.dylib -rw-r--r-- 1 root staff 641164 15 May 20:49 libvorbisenc.a lrwxrwxrwx 1 root wheel 24 21 Jun 18:08 libvorbisenc.dylib -> libvorbisenc.0.0.1.dylib -rwxr-xr-x 1 root staff 715 15 May 20:49 libvorbisenc.la -rwxr-xr-x 1 root staff 128052 15 May 20:49 libvorbisfile.0.1.0.dylib lrwxrwxrwx 1 root wheel 25 21 Jun 18:08 libvorbisfile.0.dylib -> libvorbisfile.0.1.0.dylib -rw-r--r-- 1 root staff 124000 15 May 20:49 libvorbisfile.a lrwxrwxrwx 1 root wheel 25 21 Jun 18:08 libvorbisfile.dylib -> libvorbisfile.0.1.0.dylib -rwxr-xr-x 1 root staff 721 15 May 20:49 libvorbisfile.la drwxr-xr-x 8 mathieu unknown 272 16 Jun 00:21 mplayer
Is this a clue:
www.darkhorizons-lore.com/forum_viewtopic.php?7.632
#24
Well, so far every time this problem has been encountered (3 times in the above), it has been because of some problem with the user's system. OSX is not friendly when it comes to referencing external libraries.
Let me know if you find anything out Mathieu. Have you followed the above convo and checked all the q's I asked above? I know you are thorough, so I imagine you have. But it might not hurt to double-check that libogg.a and libvorbis.a are both in your system where they are supposed to be, etc, etc, etc, as above. If so, then I would imagine it is a problem with your system.
I know I haven't checked in any changes to HEAD recently that would affect this, but I'll try to do a fresh checkout today and double-check too.
06/22/2004 (11:06 am)
:(Well, so far every time this problem has been encountered (3 times in the above), it has been because of some problem with the user's system. OSX is not friendly when it comes to referencing external libraries.
Let me know if you find anything out Mathieu. Have you followed the above convo and checked all the q's I asked above? I know you are thorough, so I imagine you have. But it might not hurt to double-check that libogg.a and libvorbis.a are both in your system where they are supposed to be, etc, etc, etc, as above. If so, then I would imagine it is a problem with your system.
I know I haven't checked in any changes to HEAD recently that would affect this, but I'll try to do a fresh checkout today and double-check too.
#25
www.versiontracker.com/dyn/moreinfo/macosx/15473
Date and time matches
I will try to know how to reinstall a clean version of this dylib.
Josh, do not lose time checking on your side, it's obviously related to this tool. :,s
06/22/2004 (11:13 am)
Ok, the only "strange" thing I have done since my last compilation is that I have installed ffmpegX, a strong tool for video/audio encoding.www.versiontracker.com/dyn/moreinfo/macosx/15473
Date and time matches
lrwxrwxrwx 1 root wheel 18 21 Jun 18:08 libogg.0.dylib -> libogg.0.2.0.d
I will try to know how to reinstall a clean version of this dylib.
Josh, do not lose time checking on your side, it's obviously related to this tool. :,s
#26
06/22/2004 (11:19 am)
Ok thanks Mathieu. :) Please let me know what the conflict ended up being anyway, if you can, just so I know for reference.
#27
I do remember it working once but not anymore.
I too have installed ffmpegX.
how do I go about installed a clean dynlib?
07/05/2004 (2:01 am)
Ok you can make the list 4 now. I too am experiencing the undefined_symbol: vorbis_info_blocksize problem.I do remember it working once but not anymore.
I too have installed ffmpegX.
how do I go about installed a clean dynlib?
#29
07/05/2004 (8:26 am)
Devon, thanks for the additional info. Don't know what exactly the deal is here, but it seems to be an OS X problem in all cases.
#30
For the record, this is on a 2.0x2 G5 with 10.3.5 and Xcode 1.5.
I also have ffmpegX installed - is that the problem?
I'm not terribly keen on the idea of reinstalling everything on my machine, but I may do that. I've had some other weird glitches with sound that I *think* are caused by Mplayer OS X (which, of course, is the reason I have ffmpegX installed) where no matter what I set the volume to the levels coming out of my speakers remain the same - nothing but a restart seems to fix it.
Any help would be greatly appreciated as I am a complete and utter newbie with Torque.
08/26/2004 (3:07 pm)
This thread seems to have died off a bit but I just got my license today and am trying to build the engine and get this same exact error... Was there ever any definitive verdict as to how to get around this?For the record, this is on a 2.0x2 G5 with 10.3.5 and Xcode 1.5.
I also have ffmpegX installed - is that the problem?
I'm not terribly keen on the idea of reinstalling everything on my machine, but I may do that. I've had some other weird glitches with sound that I *think* are caused by Mplayer OS X (which, of course, is the reason I have ffmpegX installed) where no matter what I set the volume to the levels coming out of my speakers remain the same - nothing but a restart seems to fix it.
Any help would be greatly appreciated as I am a complete and utter newbie with Torque.
#31
FFmpegX seems to be the problem. Uninstall it and use other ogg vorbis library.
08/26/2004 (5:35 pm)
@Peter,FFmpegX seems to be the problem. Uninstall it and use other ogg vorbis library.
#32
Anyway, the build problems that I see on this thread is probably far advanced than where I am. I'm getting stuck on 41 warnings and 1 undefined. Being new to XCode, I'm not sure how to correct the problem. Here is the warnings:
ld: warning -F: directory name (/Users/markfrohnmayer/torque/lib/openal/macCarb) does not exist
ld: warning multiple definitions of symbol _crc32
ld: warning multiple definitions of symbol _get_crc_table
ld: warning multiple definitions of symbol _deflate
ld: warning multiple definitions of symbol _deflateCopy
ld: warning multiple definitions of symbol _deflateReset
ld: warning multiple definitions of symbol _deflateSetDictionary
ld: warning multiple definitions of symbol _deflateInit2_
ld: warning multiple definitions of symbol _deflateEnd
ld: warning multiple definitions of symbol _deflateParams
ld: warning multiple definitions of symbol _deflateInit_
ld: warning multiple definitions of symbol _zError
ld: warning multiple definitions of symbol _zlibVersion
ld: warning multiple definitions of symbol _inflateEnd
ld: warning multiple definitions of symbol _inflateSync
ld: warning multiple definitions of symbol _inflateSyncPoint
ld: warning multiple definitions of symbol _inflate
ld: warning multiple definitions of symbol _inflateSetDictionary
ld: warning multiple definitions of symbol _inflateInit2_
ld: warning multiple definitions of symbol _inflateReset
ld: warning multiple definitions of symbol _inflateInit_
ld: warning multiple definitions of symbol _adler32
ld: warning multiple definitions of symbol _gzeof
ld: warning multiple definitions of symbol _gzclose
ld: warning multiple definitions of symbol _gzdopen
ld: warning multiple definitions of symbol _gzerror
ld: warning multiple definitions of symbol _gzflush
ld: warning multiple definitions of symbol _gzgetc
ld: warning multiple definitions of symbol _gzgets
ld: warning multiple definitions of symbol _gzopen
ld: warning multiple definitions of symbol _gzprintf
ld: warning multiple definitions of symbol _gzputc
ld: warning multiple definitions of symbol _gzputs
ld: warning multiple definitions of symbol _gzread
ld: warning multiple definitions of symbol _gzrewind
ld: warning multiple definitions of symbol _gzseek
ld: warning multiple definitions of symbol _gzsetparams
ld: warning multiple definitions of symbol _gztell
ld: warning multiple definitions of symbol _gzwrite
ld: warning prebinding disabled because of undefined symbols
ld: Undefined symbols:
It doesn't tell me what the undefined symbols is, nor do I know why I'm getting all these multiple definition warning from zlib.
Help!!!!
08/26/2004 (5:41 pm)
I just purchased my first Mac system and navigating in it is a beyotch. It's like using your mouse w/ a left hand - very cumbersome.Anyway, the build problems that I see on this thread is probably far advanced than where I am. I'm getting stuck on 41 warnings and 1 undefined. Being new to XCode, I'm not sure how to correct the problem. Here is the warnings:
ld: warning -F: directory name (/Users/markfrohnmayer/torque/lib/openal/macCarb) does not exist
ld: warning multiple definitions of symbol _crc32
ld: warning multiple definitions of symbol _get_crc_table
ld: warning multiple definitions of symbol _deflate
ld: warning multiple definitions of symbol _deflateCopy
ld: warning multiple definitions of symbol _deflateReset
ld: warning multiple definitions of symbol _deflateSetDictionary
ld: warning multiple definitions of symbol _deflateInit2_
ld: warning multiple definitions of symbol _deflateEnd
ld: warning multiple definitions of symbol _deflateParams
ld: warning multiple definitions of symbol _deflateInit_
ld: warning multiple definitions of symbol _zError
ld: warning multiple definitions of symbol _zlibVersion
ld: warning multiple definitions of symbol _inflateEnd
ld: warning multiple definitions of symbol _inflateSync
ld: warning multiple definitions of symbol _inflateSyncPoint
ld: warning multiple definitions of symbol _inflate
ld: warning multiple definitions of symbol _inflateSetDictionary
ld: warning multiple definitions of symbol _inflateInit2_
ld: warning multiple definitions of symbol _inflateReset
ld: warning multiple definitions of symbol _inflateInit_
ld: warning multiple definitions of symbol _adler32
ld: warning multiple definitions of symbol _gzeof
ld: warning multiple definitions of symbol _gzclose
ld: warning multiple definitions of symbol _gzdopen
ld: warning multiple definitions of symbol _gzerror
ld: warning multiple definitions of symbol _gzflush
ld: warning multiple definitions of symbol _gzgetc
ld: warning multiple definitions of symbol _gzgets
ld: warning multiple definitions of symbol _gzopen
ld: warning multiple definitions of symbol _gzprintf
ld: warning multiple definitions of symbol _gzputc
ld: warning multiple definitions of symbol _gzputs
ld: warning multiple definitions of symbol _gzread
ld: warning multiple definitions of symbol _gzrewind
ld: warning multiple definitions of symbol _gzseek
ld: warning multiple definitions of symbol _gzsetparams
ld: warning multiple definitions of symbol _gztell
ld: warning multiple definitions of symbol _gzwrite
ld: warning prebinding disabled because of undefined symbols
ld: Undefined symbols:
It doesn't tell me what the undefined symbols is, nor do I know why I'm getting all these multiple definition warning from zlib.
Help!!!!
#34
08/27/2004 (4:09 am)
I think what I have is an old tag. I've downloaded the head of CVS this morning and will attempt to build.
#35
Thumbs up to GG's staff. Keep up the good work.
My system:
-just upgraded to XCode 1.5
-running under OS X Panther
08/27/2004 (4:19 am)
Success! First build and the demo is running. There is a problem w/ OpenAL not funcitoning, but I'm sure the library can be upgraded to resolve that issue.Thumbs up to GG's staff. Keep up the good work.
My system:
-just upgraded to XCode 1.5
-running under OS X Panther
#36
libogg.0.2.0.dylib
libogg.0.dylib
libogg.a
libogg.dylib
libogg.la
libvorbis.0.0.1.dylib
libvorbis.0.dylib
libvorbis.a
libvorbis.dylib
libvorbis.la
libvorbisenc.0.0.1.dylib
libvorbisenc.0.dylib
libvorbisenc.a
libvorbisenc.dylib
libvorbisenc.la
libvorbisfile.0.1.0.dylib
libvorbisfile.0.dylib
libvorbisfile.a
libvorbisfile.dylib
libvorbisfile.la
from /usr/local/lib helped. Somehow XCode tries to link against the wrong libs (maybe it's ZeroLink).
08/30/2004 (8:53 am)
Just for the record. I just checked out HEAD, tried to build and got the same error while linking (tried debug build only). Removing:libogg.0.2.0.dylib
libogg.0.dylib
libogg.a
libogg.dylib
libogg.la
libvorbis.0.0.1.dylib
libvorbis.0.dylib
libvorbis.a
libvorbis.dylib
libvorbis.la
libvorbisenc.0.0.1.dylib
libvorbisenc.0.dylib
libvorbisenc.a
libvorbisenc.dylib
libvorbisenc.la
libvorbisfile.0.1.0.dylib
libvorbisfile.0.dylib
libvorbisfile.a
libvorbisfile.dylib
libvorbisfile.la
from /usr/local/lib helped. Somehow XCode tries to link against the wrong libs (maybe it's ZeroLink).
#37
08/30/2004 (1:10 pm)
That's strange you got errors while linking. Is it possible that you don't have a clean sand box or bad pbxproj file? I downloaded the head to a new folder (directory) and it built fine, and ran the demo w/o any problems.
#38
Let me know though if I'm mistaken here. :)
08/30/2004 (1:27 pm)
There are no reproducable build problems on HEAD that I know of. So far, all the problems I'm aware of due to system-specific set-ups. I don't think this is a problem any more, but you can check out this resource for some instructions too.Let me know though if I'm mistaken here. :)
#39
08/30/2004 (11:59 pm)
I only had those problems because of an old version of libvorbis that got installed some months (ffmpegx etc) ago. As I said it works after removing all those "old" libvorbis files from /usr/local/lib.
#40
08/31/2004 (12:44 am)
Okay cool. :)
Torque Owner Leo "kingDUCTtape" Altmann