On Tue, Nov 01, 2011 at 08:20:16AM -0600, Eric Blake thus spake:
On 11/01/2011 04:44 AM, Justin Clift wrote:

Fails on OSX 10.6.8, with this:

   make  all-am

   Undefined symbols:
     "_ptsname_r", referenced from:
         _virFileOpenTty in libvirt_util.a(libvirt_util_la-util.o)
   ld: symbol(s) not found
   collect2: ld returned 1 exit status
   make[3]: *** [libvirt_iohelper] Error 1
   make[3]: *** Waiting for unfinished jobs....
   make[2]: *** [all] Error 2
   make[1]: *** [all-recursive] Error 1
   make: *** [all] Error 2

Anyone feel like investigating? :)

Yeah, ptsname_r is not standardized, but is very useful; it sounds like
something gnulib should be able to fix.  I'll take a crack at it this week.

--
Eric Blake   ebl...@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

I received a similar build error for FreeBSD:

storage/storage_driver.c:507: warning: null format string [-Wformat]
  CC     libvirt_driver_storage_la-storage_backend.lo
  CC     libvirt_driver_storage_la-storage_backend_fs.lo
  CC     libvirt_driver_storage_la-storage_backend_scsi.lo
  CCLD   libvirt_driver_storage.la
  CCLD   libvirt_test.la
  CC     libvirt_iohelper-iohelper.o
  CCLD   libvirt_iohelper
./.libs/libvirt_util.a(libvirt_util_la-util.o)(.text+0x2249): In function 
`virFileOpenTty':
: undefined reference to `ptsname_r'
gmake[3]: *** [libvirt_iohelper] Error 1
gmake[3]: Leaving directory 
`/home/jhelfman/ports/devel/libvirt/work/libvirt-0.9.7/src'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory 
`/home/jhelfman/ports/devel/libvirt/work/libvirt-0.9.7/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory 
`/home/jhelfman/ports/devel/libvirt/work/libvirt-0.9.7'
gmake: *** [all] Error 2
*** Error code 1

-jgh

--
Jason Helfman
System Administrator
experts-exchange.com
http://www.experts-exchange.com/M_4830110.html
E4AD 7CF1 1396 27F6 79DD  4342 5E92 AD66 8C8C FBA5

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to