Well, if the current m4 macros don't work correctly on your system we
> should certainly fix that upstream, that's why I was asking in which way
> your patch precisely differs from what's currently upstream?
>
> Thanks,
>
> Lennart
>
> I just confused which patch you were talking about. David's on
On Tue, 18.02.14 09:50, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> > Hmm, where's the difference if I may ask? With David's commit I see no
> > empty lines in the generated output?
> >
> > Lennart
> >
> >
>
> So fine if it works for you
> In my case, systemd didn't built with dave's pacth
> Hmm, where's the difference if I may ask? With David's commit I see no
> empty lines in the generated output?
>
> Lennart
>
> --
> Lennart Poettering, Red Hat
>
So fine if it works for you
In my case, systemd didn't built with dave's pacth because of a few blank
lined left in the generated .gper
On Mon, 17.02.14 21:43, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
>
> Dave's patch was incomplete and left us with some blank lines.
> I built systemd-git with this one :
>
> http://sprunge.us/Phac
Hmm, where's the difference if I may ask? With David's commit I see no
empty lines in the
Dave's patch was incomplete and left us with some blank lines.
I built systemd-git with this one :
http://sprunge.us/Phac
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Mon, Feb 17, 2014 at 8:02 PM, Dave Reisner wrote:
> On Mon, Feb 17, 2014 at 07:35:20PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
>> On Mon, Feb 17, 2014 at 06:38:04PM +0100, arnaud gaboury wrote:
>> > > At least in systemd git nspawn places its machines in machines.slice.
>> > >
>> > > Lennart
> Doesn't build for me with the suggested ./configure options, using gperf
> 3.0.4. I applied this patch locally fix it:
>
> https://paste.xinu.at/Ffu/
>
> The problem seems to be the empty lines in the generated .gperf file.
>
> d
See my previous email, I think too all these blank lines in
src/sy
On Mon, Feb 17, 2014 at 07:35:20PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Feb 17, 2014 at 06:38:04PM +0100, arnaud gaboury wrote:
> > > At least in systemd git nspawn places its machines in machines.slice.
> > >
> > > Lennart
> > >
> > > --
> > > Lennart Poettering, Red Hat
> >
> > I
> What configure options did you use? Can you show the output from configure
> where
> it says what is enabled and what is disabled.
>
> What gperf version do you have?
>
gperf-3.0.4-4
I use the AUR mechanism to make/install package in Arch linux.Here is
part of it:
build() {
cd 'systemd'
On Mon, Feb 17, 2014 at 06:38:04PM +0100, arnaud gaboury wrote:
> > At least in systemd git nspawn places its machines in machines.slice.
> >
> > Lennart
> >
> > --
> > Lennart Poettering, Red Hat
>
> I can not build from git.
>
> ..
> GPERFsrc/core/load-fragment-gperf.c
> Empty i
> At least in systemd git nspawn places its machines in machines.slice.
>
> Lennart
>
> --
> Lennart Poettering, Red Hat
I can not build from git.
..
GPERFsrc/core/load-fragment-gperf.c
Empty input keyword is not allowed.
To recognize an empty input keyword, your code should check
On Mon, 17.02.14 13:15, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> Wouldn't it be preferable to have a machine.slice instead of a
> machine.scope under the system.slice? Does it make any big difference
> to run/manage the container ?
At least in systemd git nspawn places its machines in m
Hi all,
I set up a linux container on my host.
Here are some basic infos:
- Host + guest running Archlinux
On host:
- custom kernel on host with user space set
- audit=0 as kernel parameter
- the guest OS is mounted in my rootfs at /dahlia with a symlink to
/var/lib/container
gabx@hortensia ➤➤ ~
13 matches
Mail list logo
