[FIXED] Transission won't compile on Solaris 10: strsep

[oh_noes]

I'm trying to get Transmission 2.12 (Daemon) installed on Solaris 10 Update 9 x86.

I'm using GCC make and a bunch of packages from SUNFreeware. I'm making progress, but I'm stuck on the following.

Code: Select all

$ cd transmission-2.12

$ export LIBCURL_CFLAGS="-I/usr/local/include"
$ export LIBCURL_LIBS="-L/usr/local/lib"
$ export LD_LIBRARY_PATH="/usr/local/lib"

$ ./configure CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" LIBCURL_CFLAGS="-I/usr/include/curl" LIBCURL_LIBS="-L/usr/lib -lc -lcurl -lgss -lidn -lsldap -lldap -lsocket -lnsl -lz -lssl -lcrypto" --prefix=/usr/local/transmission --enable-daemon --enable-cli --disable-nls --disable-gtk  --with-zlib="/usr/local" --with-zlib-includes="/usr/local"
$ make

`make` fails with the following error:

Code: Select all

make[1]: Leaving directory `/export/home/transmission/transmission-2.12/libtransmission'
Making all in utils
make[1]: Entering directory `/export/home/transmission/transmission-2.12/utils'
  CC     create.o
  CCLD   transmission-create
Undefined                       first referenced
 symbol                             in file
strsep                              ../libtransmission/libtransmission.a(makemeta.o)
ld: fatal: Symbol referencing errors. No output written to transmission-create
collect2: ld returned 1 exit status
make[1]: *** [transmission-create] Error 1
make[1]: Leaving directory `/export/home/transmission/transmission-2.12/utils'
make: *** [all-recursive] Error 1

Undefined symbol strsep
first referenced in file ../libtransmission/libtransmission.a(makemeta.o)


With a bit of research, it turns out strsep is not supported on Solaris 10 (it's not portable).

Any idea's?

[Jordan]

Solaris doesn't support strsep()? That doesn't seem right. Are you sure?

[Jordan]

Sure enough.

Fixed in trunk for 2.13, which will be out shortly.

https://trac.transmissionbt.com/ticket/3813

[oh_noes]

Thanks. I managed to instal 2.12 by changing meta*.c strsep() to strtok().

Thanks for fixing this bug in 2.13.