From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] pckages/sconeserver: fix build with gcc-6
Date: Sun, 28 Aug 2016 20:06:03 +0200 [thread overview]
Message-ID: <20160828180603.GD5758@free.fr> (raw)
In-Reply-To: <CAFt09wOQ9fOLGkdbM-Jtuw9G_tizsO8103x317ADp2Rf+YU7wQ@mail.gmail.com>
Matt, All,
On 2016-08-27 07:38 -0500, Matthew Weber spake thusly:
> On Thu, Aug 25, 2016 at 3:26 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Hello,
> >
> > On Thu, 25 Aug 2016 09:45:53 +0200, Yann E. MORIN wrote:
> >> We simply bump the version rather than backport the patch, as there has
> >> been only very few, minor commits in-between.
> >>
> >> Fixes:
> >> http://autobuild.buildroot.org/results/fa7/fa7881c6ffb821a2aff139f95ba53c96d6e2b942/
> >> http://autobuild.buildroot.org/results/749/749fbd6cc505f6f3c0cccfeb63be6deddab8fba5/
> >>
> >> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> >>
> <snip>
>
> Looks like the new revision has a failed build.
> http://autobuild.buildroot.org/results/e92/e929799366e6f574c7b08d8635b18623afd3e3e1//
>
> ModuleLoader.cpp:29:19: fatal error: dlfcn.h: No such file or directory
> #include <dlfcn.h>
> ^
> I didn't have a chance to check if the conf opts for disable-load
> works on this package yet but that might fix it (assuming it can be
> statically built).
>
> When I first rebuilt, I tried just doing a "make clean sconeserver"
> and got this error.
>
> configure.in:118: error: possibly undefined macro: AC_MSG_FAILURE
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> configure.in:120: error: possibly undefined macro: AC_MSG_WARN
> autoreconf: /home/mlweber/buildroot/output/host/usr/bin/autoconf
> failed with exit status: 1
> package/pkg-generic.mk:191: recipe for target
> '/home/mlweber/buildroot/output/build/sconeserver-d659468cd164e6a6cc12932cc6780566b04f8328/.stamp_configured'
> failed
>
> I haven't had a chance to look into why but thought I'd get it out there.
OK, so I finally had the time to give it a shot:
- the autoreconf issue is because it uses pkg-config macros, and it
was missing a dependency on host-pkgconf,
- the build issue is because a pure static uClibc build does not
install dlfcn.h and can't do dynamic loading with dlopen().
Both issues already existed with the previous version, we just did not
notice them...
So: thanks for noticing this time! ;-)
I'll send the patches in a moment.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-08-28 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 7:45 [Buildroot] [PATCHv2] pckages/sconeserver: fix build with gcc-6 Yann E. MORIN
2016-08-25 8:26 ` Thomas Petazzoni
2016-08-27 12:38 ` Matthew Weber
2016-08-27 14:09 ` Yann E. MORIN
2016-08-28 18:06 ` Yann E. MORIN [this message]
2016-08-28 20:53 ` Matthew Weber
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=20160828180603.GD5758@free.fr \
--to=yann.morin.1998@free.fr \
--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