undefined symbols (was: Re: Architecture mixup)

Ryan Schmidt ryandesign at macports.org
Thu May 17 13:11:39 PDT 2012


On May 17, 2012, at 01:25, Ian Wadham wrote:

> Linking CXX executable ktuberling.app/Contents/MacOS/ktuberling
> Undefined symbols for architecture x86_64:
>  "KStandardGameAction::gameNew(QObject const*, char const*, QObject*)", referenced from:
>      TopLevel::setupKAction()      in toplevel.o
>  "KStandardGameAction::load(QObject const*, char const*, QObject*)", referenced from:
>      TopLevel::setupKAction()      in toplevel.o
>  "KStandardGameAction::save(QObject const*, char const*, QObject*)", referenced from:
>      TopLevel::setupKAction()      in toplevel.o
>  "KStandardGameAction::print(QObject const*, char const*, QObject*)", referenced from:
>      TopLevel::setupKAction()      in toplevel.o
>  "KStandardGameAction::quit(QObject const*, char const*, QObject*)", referenced from:
>      TopLevel::setupKAction()      in toplevel.o
> ld: symbol(s) not found for architecture x86_64
> collect2: ld returned 1 exit status
> make[2]: *** [ktuberling/ktuberling.app/Contents/MacOS/ktuberling] Error 1
> make[1]: *** [ktuberling/CMakeFiles/ktuberling.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs….

The only reason I can think of for symbols being undefined, is those symbols not being there. You'll have to ask the makers of the library if the symbols are really there, and if they are, then ask the makers of the program you're trying to compile why it can't find the symbols.



More information about the macports-users mailing list