Heres a question for anyone awake at this hour, does icecast2 require libpthread? I'm trying to build it on a freebsd 4.3 box, and it wants to link against libpthread. If this is not required on the freebsd platform, then is it safe to just take out of the makefile? Thanks Mike -- <mystica@darktech.org> --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> Heres a question for anyone awake at this hour, does icecast2 require > libpthread? I'm trying to build it on a freebsd 4.3 box, and it wants to > link against libpthread. If this is not required on the freebsd > platform, then is it safe to just take out of the makefile?It needs pthreads. FreeBSD provides this in the reentrant c library. For FreeBSD, you should remove -lpthread from LIBS and add -pthread to CFLAGS. I believe this should be the only change required. I will fix FreeBSD building in the next few days (or at least this is my intention) as well as Win32 building. Once this is done, I'm planning an alpha1 release of icecast 2.0 to give people something to concretely test, etc. jack. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Mon, 22 Oct 2001 00:07:39 -0600 Jack Moffitt <jack@xiph.org> wrote:> It needs pthreads. FreeBSD provides this in the reentrant c library. > > For FreeBSD, you should remove -lpthread from LIBS and add -pthread to > CFLAGS. I believe this should be the only change required. > > I will fix FreeBSD building in the next few days (or at least this is my > intention) as well as Win32 building. > > Once this is done, I'm planning an alpha1 release of icecast 2.0 to give > people something to concretely test, etc. > > jack.That worked, but I do get a few linking warnings. Are these serious? /usr/lib/libc.so.4: WARNING! setkey(3) not present in the system! /usr/lib/libc.so.4: warning: this program uses gets(), which is unsafe. /usr/lib/libc.so.4: warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so.4: WARNING! des_setkey(3) not present in the system! /usr/lib/libc.so.4: WARNING! encrypt(3) not present in the system! /usr/lib/libc.so.4: warning: tmpnam() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so.4: warning: this program uses f_prealloc(), which is stupid. /usr/lib/libc.so.4: WARNING! des_cipher(3) not present in the system! /usr/lib/libc.so.4: warning: tempnam() possibly used unsafely; consider using mkstemp() Mike -- <mystica@darktech.org> --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.