Hmm, I don't see any warnings at all, compiling with CLang on Linux.On Tue, Oct 01, 2013 at 08:35:41AM -0700, Jason Helfman wrote:
> On Tue, Oct 1, 2013 at 3:17 AM, Christophe Fergeau <cfergeau@redhat.com>wrote:
>
> > Hi,
> >
> > On Fri, Sep 27, 2013 at 12:09:43PM -0700, Jason Helfman wrote:
> > > On Thu, Sep 26, 2013 at 6:06 AM, Christophe Fergeau <cfergeau@redhat.com
> > >wrote:
> > > > On Wed, Sep 25, 2013 at 09:31:52AM -0700, Jason Helfman wrote:
> > > > > When compiling libvirt-glib with CLANG, I get the following error.
> > > > >
> > > > > 16 warnings generated.
> > > > > CCLD libvirt-glib-1.0.la
> > > > > GEN LibvirtGLib-1.0.gir
> > > > > /usr/local/lib/libvirt.so: undefined reference to
> > > > `__stack_chk_fail_local'
> > > > > clang: error: linker command failed with exit code 1 (use -v to see
> > > > > invocation)
> > >
> > > http://people.freebsd.org/~jgh/files/libvirt-glib-make.log
> > >
> > > It was clean, yes.
> >
> > Rereading that log more carefully, it's complaining about a missing symbol
> > in the installed libvirt.so, not in one of the .so that was just built. Are
> > other applications able to link against libvirt? Was libvirt compiled with
> > clang or gcc?
> >
> > Christophe
> >
>
> That is odd. I de-installed libvirt, and re-installed it. After this
> libvirt-glib compiled with CLANG, and didn't result in any failure.
> Many warnings, but good to know it does compile.
Please let us know what you're seeing on BSD ?
Daniel