From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/2] Fix logrotate autobuild failure
Date: Sun, 01 Mar 2015 22:35:31 +0100 [thread overview]
Message-ID: <87vbikwgd8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1425244013-2509-1-git-send-email-fabio.porcedda@gmail.com> (Fabio Porcedda's message of "Sun, 1 Mar 2015 22:06:51 +0100")
>>>>> "Fabio" == Fabio Porcedda <fabio.porcedda@gmail.com> writes:
> This patch set fix a logrotate autobuild failure:
> http://autobuild.buildroot.net/results/159bf5730414ca7f73dcdae95090177355193636
> http://autobuild.buildroot.net/results/ebe6ab7fc0f2cff98de06b3dc374730da9e9e4f2
> v3:
> - popt: instead of using sed add a patch and send it upstream
> - logrotate: improve commit message
> v2:
> - logroate: instead of adding a patch just overwrite from the command line the
> LOADLIBES variable
Hmm, while this is an improvement I still see failures.
I could only get popt to pull in the gettext/libintl dependency if I
added libiconv, but as we don't add libiconv to Libs.private we then end
up with linker issues for it in logrotate:
/home/peko/source/buildroot/output/host/usr/bin/arm-linux-gcc -Os -static logrotate.o log.o config.o basenames.o -L/home/peko/source/buildroot/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib -lpopt -o logrotate
logrotate.o: In function `compressLogFile':
/home/peko/source/buildroot/output/build/logrotate-3.8.7/logrotate.c:537: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
/home/peko/source/buildroot/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libpopt.a(poptint.o): In function `POPT_fprintf':
poptint.c:(.text+0x534): undefined reference to `libiconv_open'
poptint.c:(.text+0x58c): undefined reference to `libiconv'
poptint.c:(.text+0x5b8): undefined reference to `libiconv'
poptint.c:(.text+0x62c): undefined reference to `libiconv_close'
collect2: ld returned 1 exit status
<builtin>: recipe for target 'logrotate' failed
So I have left out this series for 2015.02.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-03-01 21:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 21:06 [Buildroot] [PATCH v3 0/2] Fix logrotate autobuild failure Fabio Porcedda
2015-03-01 21:06 ` [Buildroot] [PATCH v3 1/2] popt: add to the "popt.pc" file the libintl library Fabio Porcedda
2015-03-04 22:27 ` Thomas Petazzoni
2015-03-01 21:06 ` [Buildroot] [PATCH v3 2/2] logrotate: use pkg-config for the opt library Fabio Porcedda
2015-03-04 22:29 ` Thomas Petazzoni
2015-03-04 23:38 ` Fabio Porcedda
2015-03-05 8:28 ` Thomas Petazzoni
2015-03-05 8:43 ` Fabio Porcedda
2015-03-01 21:35 ` Peter Korsgaard [this message]
2015-03-01 21:43 ` [Buildroot] [PATCH v3 0/2] Fix logrotate autobuild failure Fabio Porcedda
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=87vbikwgd8.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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