From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] libnl: bump to version 3.0
Date: Thu, 28 Apr 2011 16:19:03 +0200 [thread overview]
Message-ID: <4DB97757.3090305@visionsystems.de> (raw)
In-Reply-To: <20110428140919.77d3027f@surf>
Am 28.04.2011 14:09, schrieb Thomas Petazzoni:
> On Thu, 28 Apr 2011 09:30:32 +0200
> Yegor Yefremov <yegor_sub1@visionsystems.de> wrote:
>
>> I would leave AUTORECONF option. On my old build system openSUSE
>> 10.3 libnl-3.0 would compile only if reconfigured, otherwise it
>> cannot find some header files. On my new Ubuntu 11.04 distro I don't
>> have such problems. What do you think about this?
> I'd say we need more specific details on the header files issue rather
> than blindly deciding to use the <pkg>_AUTORECONF=YES big hammer :-)
You're right. I tried it once again and it seems to fail only if I clean the whole buildroot and then start again. Build crashes with something like that:
CC addr.lo
CC attr.lo
CC cache.lo
CC cache_mngr.lo
CC cache_mngt.lo
CC data.lo
CC error.lo
CC handlers.lo
CC msg.lo
CC nl.lo
CC object.lo
CC socket.lo
CC utils.lo
GEN route/cls/ematch_syntax.c
CC route/cls/ematch.lo
GEN route/cls/ematch_grammar.c
GEN route/pktloc_syntax.c
GEN route/pktloc_grammar.c
CC route/pktloc.lo
route/pktloc.c:39:27: fatal error: pktloc_syntax.h: No such file or directory
compilation terminated.
cd .. && /bin/sh ./config.status lib/defs.h
CC genl/ctrl.lo
but if I run make again everything gets built like a charm. Perhaps this is caused by -j16. So no need for big hammer :-)
Best regards,
Yegor
next prev parent reply other threads:[~2011-04-28 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 12:59 [Buildroot] [PATCH v3] libnl: bump to version 3.0 Yegor Yefremov
2011-04-28 7:30 ` Yegor Yefremov
2011-04-28 12:09 ` Thomas Petazzoni
2011-04-28 14:19 ` Yegor Yefremov [this message]
2011-04-28 14:30 ` Gustavo Zacarias
2011-04-28 15:05 ` Yegor Yefremov
2011-04-28 15:29 ` Peter Korsgaard
2011-05-04 7:29 ` Yegor Yefremov
2011-04-28 13:21 ` Gustavo Zacarias
2011-05-15 7:59 ` 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=4DB97757.3090305@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--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