Date: Mon, 13 Nov 2006 15:56:22 -0500 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: freebsd-ports@freebsd.org Cc: freebsd-emulation@freebsd.org, wxs@atarininja.org, martinko <gamato@users.sf.net> Subject: Re: emulators/qemu-launcher: unable to launch Message-ID: <44ejs73w21.fsf@be-well.ilk.org> In-Reply-To: <44r6w73x1p.fsf@be-well.ilk.org> (Lowell Gilbert's message of "Mon, 13 Nov 2006 15:34:58 -0500") References: <45563E71.3050403@users.sf.net> <44slgo6675.fsf@be-well.ilk.org> <45575D66.6000100@users.sf.net> <44r6w73x1p.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> writes: > martinko <gamato@users.sf.net> writes: > >> Lowell Gilbert wrote: >>> martinko <gamato@users.sf.net> writes: >>> >>> >>>> Hello list, >>>> >>>> I've just compiled and installed emulators/qemu-launcher and this is >>>> what I've got when trying to run it: >>>> >>>> $ qemu-launcher >>>> /libexec/ld-elf.so.1: /usr/local/lib/libgthread-2.0.so.0: Undefined >>>> symbol "pthread_getschedparam" >>>> >>>> What's wrong please? What am I to do now? >>>> >>> >>> When you installed the port, it printed out the pkg-message file for >>> the port, which has the answer for this problem and a number of >>> others. Specifically: >>> - qemu now uses aio at least for ide dma, so if you get `Bad system call' >>> crashes that is because aio is not (kld)loaded. >>> >>> >>> >> >> Lowell, >> >> You're obviously right. The message must have scrolled off the screen >> or something. Usually I notice and read pkg-messages. Sorry. >> >> But yours was an answer to a different question of mine. This thread is >> regarding qemu-launcher and has nothing to do with aio.ko. (I just >> checked if there isn't anything in its pkg-message:)) >> >> Do you happen to know a solution to this issue too please ? > > My apologies; I seem to have cut and pasted into the wrong windows. > > This is a problem with how glib links into the pthreads libraries. > pthread_getschedparam is definitely supposed to be invoked from there, > and on -STABLE, at least, that symbol is in libpthread. Is that the > case on your system? When you build glib, is libpthread found? Oops; never mind. I can reproduce this also.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44ejs73w21.fsf>