xorg build error: needs uuid
Jeremy C. Reed
reed at reedmedia.net
Mon Jul 7 10:04:18 PDT 2008
On Mon, 7 Jul 2008, Dan Williams wrote:
> > > I got an error during configuration of libSM, it wanted a package "uuid". I
> > > foound (using google) a linux package named libuuid, but since I don't run
> > > Linux, I'd never seen it on my FreeBSD-current system, not anywhere in the
> > > sources, not even in the ports. Is this soomewhere in the xorg sources? I
> > > searched for *uuid* but didn't find it.
> > >
> > > If it's a linux-only thing, is it reasonable to make xorg dependent upon it (or,
> > > maybe I'm jumping to conclusions here). I need to find some way to get past this.
> >
> > I see that also on NetBSD.
> >
> > FreeBSD and NetBSD both have uuid.h and uuidgen(2) and uuid(3).
> >
> > The FreeBSD package is called ports/misc/e2fsprogs-libuuid (but I don't
> > think that package should be needed as the libc support should be fine).
>
> What package are the Free/NetBSD uuid.h file and functions provided by?
> Are the function prototypes compatible with libuuid?
Not in a package. They are in libc.
I am not sure about compatibility -- the functions are named differently.
Man page says "The identifiers are generated according to the syntax and
semantics of the DCE version 1 variant of universally unique identifiers."
> > The libSM/src/sm_genid.c checks for HAVE_LIBUUID so failing at
> > configuration time is not right. It has other ways to
> > "SmsGenerateClientID".
>
> Not really; if you explicitly specify on the configure line that you
> want to use libuuid, you really, really do want configure-time to fail
> if it's missing. Otherwise, unrelated changes to your system can
> _silently_ change intended behavior of the X server based on what
> packages were installed at compile-time regardless of your explicit
> intention at compile-time. That's bad.
>
> Current expected behavior is:
>
> 1) if --with-libuuid specified, fail at configure time if libuuid not
> found
> 2) if no --with-libuuid is specified, keep pre-patch behavior and don't
> use libuuid
I understand that. But by default it fails (doesn't fall back).
> > A good example is in the Apache apr source.
More information about the xorg
mailing list