From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] rsync fails to build
Date: Sat, 29 Mar 2014 14:30:57 +0100 [thread overview]
Message-ID: <20140329143057.6e6aa65a@skate> (raw)
In-Reply-To: <6699457346BD4E4E8F8D768D2249294C@JohanW7>
Dear Sagaert Johan,
On Sat, 29 Mar 2014 14:11:56 +0100, Sagaert Johan wrote:
> With the latest pull :
>
> Rsync build seems to be broken
>
> S=64 -c xattrs.c -o xattrs.o
> /home/brcpy/output/host/usr/bin/ccache /home/brcpy/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc -std=gnu99 -I. -I.
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -DHAVE_CONFIG_H -Wall -W -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -c progress.c -o progress.o
> /home/brcpy/output/host/usr/bin/ccache /home/brcpy/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc -std=gnu99 -I. -I.
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -DHAVE_CONFIG_H -Wall -W -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -c pipe.c -o pipe.o
> /home/brcpy/output/host/usr/bin/ccache /home/brcpy/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc -std=gnu99 -I. -I.
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -DHAVE_CONFIG_H -Wall -W -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -c params.c -o params.o
> /home/brcpy/output/host/usr/bin/ccache /home/brcpy/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc -std=gnu99 -I. -I.
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -DHAVE_CONFIG_H -Wall -W -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -c loadparm.c -o loadparm.o
> In file included from xattrs.c:25:0:
> lib/sysxattrs.h:4:24: fatal error: attr/xattr.h: No such file or directory
> compilation terminated.
It builds fine here.
Can you show the output of the configure step? I believe it might be
detecting something from your host machine.
Best regards,
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 13:30 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 [this message]
2014-03-29 16:39 ` Sagaert Johan
2014-03-29 17:00 ` Thomas Petazzoni
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=20140329143057.6e6aa65a@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.