Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Has anybody got systemd to work?
Date: Mon, 18 Jun 2012 14:58:06 +0200	[thread overview]
Message-ID: <4FDF25DE.20507@free-electrons.com> (raw)
In-Reply-To: <4FDF24E2.6020603@free-electrons.com>

Le 18/06/2012 14:53, Maxime Ripard a ?crit :
> Hi Dmitry,
> 
> I was just replying to your previous mail.
> 
> Le 18/06/2012 14:46, Dmitry Golubovsky a ?crit :
>> Maxime: do you use an alternative toolchain with systemd?
> 
> After a bit of testing, it seems indeed that the bug is uclibc-only, and
> didn't encountered it as I do most of my testing using glibc.
> 
> Anyway, if it is only the %ms thing that is breaking systemd on uclibc,
> it shouldn't be such a big problem. Quickly grepping the systemd source
> code returns 17 occurences of such case, so a patch is definitely doable.
> 
> I won't have much time, do you mind doing so and sending us the patch so
> that it could get included ?

Also, it seems that the %m modifier support has been merged 3 weeks ago
in uclibc:

http://git.uclibc.org/uClibc/commit/libc/stdio/_scanf.c?id=8cfb43de636faa401634340d1a18404844f9ba5a

Looks like we will definitely need a patch :)

-- 
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-06-18 12:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  2:45 [Buildroot] Has anybody got systemd to work? Dmitry Golubovsky
2012-06-18  7:15 ` Attila Kinali
2012-06-18 12:46   ` Dmitry Golubovsky
2012-06-18 12:53     ` Maxime Ripard
2012-06-18 12:58       ` Maxime Ripard [this message]
2012-06-18 13:02       ` Dmitry Golubovsky
2012-06-18 13:21       ` Attila Kinali
2012-06-18 13:32         ` Dmitry Golubovsky
2012-06-18 18:59           ` Dmitry Golubovsky
2012-06-18 19:43             ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FDF25DE.20507@free-electrons.com \
    --to=maxime.ripard@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox