From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] rsync fails to build
Date: Sat, 29 Mar 2014 18:00:38 +0100 [thread overview]
Message-ID: <20140329180038.7acf5143@skate> (raw)
In-Reply-To: <9E4B04B54DB642238FDE42DB9E40DE73@JohanW7>
Dear Sagaert Johan,
On Sat, 29 Mar 2014 17:39:20 +0100, Sagaert Johan wrote:
> It contains some suspected lines :
> (I am using gcc 4.6.x)
>
> checking attr/xattr.h usability... yes
> checking attr/xattr.h presence... no
> configure.sh: WARNING: attr/xattr.h: accepted by the compiler, rejected by the preprocessor!
> configure.sh: WARNING: attr/xattr.h: proceeding with the compiler's result
> checking for attr/xattr.h... Yes
>
> My older (working)build does not have these warnings, but the attr package is selected due to the udev selection and udev extras.
>
> (Did you build with the packages attr and acl disabled ?)
I had acl and attr disabled, but I tried again with them enabled, and
it still works.
> I will do a build using gcc 4.8.x to see if this warning still exists.
I don't think it's going to change anything. Can you do a complete
"make clean all" cycle to verify that the error still exists? If it
does, can you please post on http://code.bulix.org the contents of
rsync config.log file, as well as the complete build output of the
rsync package, from its extraction step?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-29 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 13:11 [Buildroot] rsync fails to build Sagaert Johan
2014-03-29 13:30 ` Thomas Petazzoni
2014-03-29 16:39 ` Sagaert Johan
2014-03-29 17:00 ` Thomas Petazzoni [this message]
2014-03-29 22:11 ` Sagaert Johan
2014-03-29 22:20 ` Thomas Petazzoni
2014-03-31 0:36 ` Sagaert Johan
2014-03-31 8:26 ` Thomas Petazzoni
2014-03-31 12:31 ` Sagaert Johan
2014-04-02 5:53 ` Arnout Vandecappelle
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=20140329180038.7acf5143@skate \
--to=thomas.petazzoni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.