[SOLVED] compiling error in sl-current "undefined reference to symbol"?

marbangens · 04-04-2013, 04:24 PM

Hello everyone!
I have trouble compiling gnash that I can't solve on my own.
Tried specify LDFLAGS="-lboost_system"
The output is

Code:

  CXXLD  dump-gnash
/usr/lib64/gcc/x86_64-slackware-linux/4.8.0/../../../../x86_64-slackware-linux/bin/ld: dump_gnash-gnash.o: undefined reference to symbol '_ZN5boost6system15system_categoryEv'
/usr/lib64/gcc/x86_64-slackware-linux/4.8.0/../../../../x86_64-slackware-linux/bin/ld: note: '_ZN5boost6system15system_categoryEv' is defined in DSO /usr/lib64/../lib64/libboost_system.so.1.53.0 so try adding it to the linker command line
/usr/lib64/../lib64/libboost_system.so.1.53.0: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
make[4]: *** [dump-gnash] Error 1
make[4]: Leaving directory `/tmp/SBo/gnash-0.8.10/gui'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/tmp/SBo/gnash-0.8.10/gui'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/tmp/SBo/gnash-0.8.10/gui'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/SBo/gnash-0.8.10'
make: *** [all] Error 2

It seems like -lboost_system don't work. Also found

Code:

Configured paths for x86_64-slackware-linux-gnu are:
        ...
        BOOST flags are: -I/usr/X11/include
        BOOST libs are: -L/usr/lib64 -lboost_thread -lboost_program_options -lboost_iostreams
        BOOST libs for cygnal are:  -lboost_serialization -lboost_date_time
        ...

wildwizard · 04-05-2013, 05:33 AM

Have you got the Apr 3rd updates yet? There is a patch there that restores some functionality to the linker that may be required.

marbangens · 04-07-2013, 09:51 AM

This must be about gnash's configure.ac file.
The slackbuild script uses autoreconf don't include -lboost_system.
I think so because configure and compiling works on the git tree.

Code:

aclocal.m4:16: warning: this file was generated for autoconf 2.64.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.

I must rewrite the buildscrip for a git version