From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] Build failed for package avahi
Date: Thu, 31 Jul 2014 10:42:51 +0200 [thread overview]
Message-ID: <53DA018B.6050507@posteo.de> (raw)
In-Reply-To: <20140731093821.2c5d8ac3@free-electrons.com>
Dear Thomas,
On 07/31/2014 09:38 AM, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Thu, 31 Jul 2014 09:24:21 +0200, J?rg Krause wrote:
>
>>>> checking how to run the C++ preprocessor... /lib/cpp
>>>> configure: error: in
>>>> `/home/joerg/Freescale/buildroot/output/build/avahi-0.6.31':
>>>> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
>>>> See `config.log' for more details
>>> Can you post the contents of output/build/avahi-0.6.31/config.log ?
>> I attached the config.log.
> Problem is:
>
> configure:13407: /lib/cpp conftest.cpp
> ./configure: line 2321: /lib/cpp: No such file or directory
>
> Autotools (or parts of it) expect /lib/cpp to be a symbolic link to the
> C preprocessor. However, certain distributions (I think Archlinux) are
> no longer installing this symbolic link.
You're right, /lib/cpp is missing on Arch linux.
>
> I'm not sure what is to blame here: the distro not creating
> the /lib/cpp symbolic link, or the autotools using this symbolic link?
In my opinion autotools should be fixed. I have no experience with
autotools. How can this be done?
Best regards
J?rg Krause
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140731/80f82c11/attachment.html>
prev parent reply other threads:[~2014-07-31 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 22:37 [Buildroot] Build failed for package avahi Jörg Krause
2014-07-30 23:04 ` Thomas Petazzoni
2014-07-31 7:24 ` Jörg Krause
2014-07-31 7:38 ` Thomas Petazzoni
2014-07-31 8:42 ` Jörg Krause [this message]
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=53DA018B.6050507@posteo.de \
--to=jkrause@posteo.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 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.