[Openchrome-users] Openchrome on OBSD 4.2 working
mrdubya
userforum
Thu Jan 17 05:39:46 PST 2008
Re: Openchrome on OBSD 4.2 working
> mrdubya wrote:
> > Rather than have to modify the
> > Makefile to cope with shells that may or may not do backslash
> > interpretation It may be simpler just to modify the call to
> > xf86Msg() to use the compiler's string concatenation -
> >
> > xf86Msg(X_NOTICE, BUILDCOMMENT"\n");
>
> Done. Thanks for the suggestion.
No probs. Confirmed that it works with the latest trunk version.
> > For some reason svnversion.h.tmp is owned by root
>
> Only when the compilation was done as root once, no?
That would be a no (:wink:)
I did a clean checkout, build on a joe bloggs user account and the install as root. After this the svnversion.h.tmp file was owned by root, so I assume the install process is regenerating the .tmp file for some reason. More spelunking to be done.
> > > As far as I know /usr/lib/xorg is the standard place nowadays
> > > and most distros make a /usr/X11R6 -> ../usr symlink or
> > > similar.
> >
> > On OBSD it is /usr/X11R6 by design. Is there an autogen --?dir
> > that can be used to change the path?
>
> See ./configure --help:
>
> --with-xorg-module-dir=DIR
> Default xorg module directory
> [default=$libdir/xorg/modules]
That would be the one, and yes it happily works.
So for OBSD you need to specify the mandir and with-xorg-module-dir and then everything just falls into place. Nice one, many thanks.
TTFN
MW
----
Reply Link: <http://wiki.openchrome.org/tikiwiki/tiki-view_forum_thread.php?forumId=1&comments_reply_threadId=4558&comments_parentId=4442&post_reply=1#form>
More information about the Openchrome-users
mailing list