From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/openswan: not available on musl
Date: Sun, 31 Jul 2016 14:47:47 +0200 [thread overview]
Message-ID: <1469969267.9042.2.camel@embedded.rocks> (raw)
In-Reply-To: <1469958682-6087-1-git-send-email-bernd.kuhls@t-online.de>
On So, 2016-07-31 at 11:51 +0200, Bernd Kuhls wrote:
> After fixing the usual sys/cdefs.h and _P stuff the build still fails
> because Openswan makes use of GLOB_ functions
>
> /home/bernd/buildroot/br4/output/build/openswan-
> 2.6.48/lib/libipsecconf/parser.l:200:29: error: ?GLOB_BRACE?
> undeclared (first use in this function)
> ??????globresult = glob(try, GLOB_BRACE, NULL, &globbuf);
> ?????????????????????????????^
> /home/bernd/buildroot/br4/output/build/openswan-
> 2.6.48/lib/libipsecconf/parser.l:200:29: note: each undeclared
> identifier is reported only once for each function it appears in
> /home/bernd/buildroot/br4/output/build/openswan-
> 2.6.48/lib/libipsecconf/parser.l:207:41: error: ?GLOB_NOMAGIC?
> undeclared (first use in this function)
> ???????globresult = glob(try, GLOB_BRACE|GLOB_NOMAGIC, NULL,
> &globbuf);
>
> https://github.com/xelerance/Openswan/blob/master/lib/libipsecconf/pa
> rser.l#L200
> https://github.com/xelerance/Openswan/blob/master/lib/libipsecconf/pa
> rser.l#L207
> [...]
> ?????????????????????????????????????????^
> which musl does not support:
> http://www.openwall.com/lists/musl/2013/09/16/1
>
Maybe we can add libglob [1] as a package and add it as a musl
dependencies like we do it with netbsd-queue?
[1]?https://github.com/voidlinux/libglob
Best regards
J?rg Krause
next prev parent reply other threads:[~2016-07-31 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 9:51 [Buildroot] [PATCH 1/1] package/openswan: not available on musl Bernd Kuhls
2016-07-31 12:47 ` Jörg Krause [this message]
2016-07-31 16:05 ` Baruch Siach
2016-07-31 21:01 ` Thomas Petazzoni
2016-08-01 18:24 ` Jörg Krause
2016-08-01 18:28 ` Bernd Kuhls
2016-08-28 16:47 ` Yann E. MORIN
2016-08-29 15:57 ` Peter Korsgaard
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=1469969267.9042.2.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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