guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Running guix-daemon as an unprivileged user (Was: [PATCH] syscalls:


From: 韋嘉誠
Subject: Re: Running guix-daemon as an unprivileged user (Was: [PATCH] syscalls: setns: Skip binding if there is no such C function.)
Date: Mon, 17 Aug 2015 16:27:38 +0200

On Mon, Aug 17, 2015 at 3:42 PM, Claes Wallin (韋嘉誠)
<address@hidden> wrote:
> On Mon, Aug 17, 2015 at 10:33 AM, Eric Bavier
> <address@hidden> wrote:

>>> https://www.gnu.org/software/guix/manual/guix.html#Build-Environment-Setup
>>>
>>> "If you are installing Guix as an unprivileged user, it is still
>>> possible to run guix-daemon provided you pass --disable-chroot."
>>>
>>
>> I have experimented with this a bit lately.  It works to some extent,
>> but I have had to apply a few patches to some package recipes.  Some
>> packages have failing tests (where presumably they would pass or be
>> skipped in the chroot), which I have disabled for the time being just
>> to move along.
>>
>> I can post a few of the patches to the ML later.
>
> I'm doing this from git now, as opposed to doing it from the tarball
> earlier, because I want that setns patch.
>
> I have compiled gettext, m4, autoconf, automake and guile and its
> deps, installed in /home/myuser/.local.

And now I added sqlite and pkg-config as well, because looking at the
diff between tarball configure and my configure told me those were
missing. This helped me forward!


> Rather than run ./bootstrap, I've had to run gettextize, aclocal,
> autoreconf -vi (no -f!) with CPATH, LIBRARY_PATH and maybe AC_MACRODIR
> (probably not necessary), and I managed to get a ./configure, but it
> now tells me:


Now I'm doing this:

git clean -fxd && # recover from previous attempts
git checkout HEAD . && # ditto
gettextize --po-dir=po{/guix,/packages,} &&
sed -re '/^[[:blank:]]*po\/(guix|packages)\/Makefile.in[[:blank:]]*$/d'
-i configure.ac && # because gettextize creates redundant entries for
these, over which alocal gets very upset
aclocal -I m4 &&
AUTOPOINT=true autoreconf -vi


And after a "LIBRARY_PATH=/home/myuser/.local/lib
CPATH=/home/myuser/.local/include ./configure
--prefix=/home/eclewal/.local" it looks like I'm able to compile!

Thanks for putting up with my rubber-ducking.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]