From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/crosstool-ng: update to 1.17.0
Date: Sun, 09 Dec 2012 22:18:44 +0100 [thread overview]
Message-ID: <50C50034.7040709@googlemail.com> (raw)
In-Reply-To: <201212092137.46147.yann.morin.1998@free.fr>
Hello Yann, Hello Peter,
Am 09.12.2012 21:37, schrieb Yann E. MORIN:
>> Unfortunately it doesn't seem to build here (ppl compilation issue):
>>
>> [ERROR] /home/peko/source/buildroot/testctng/build/build-toolchain/.build/src/ppl-0.10.2/src/Interval.defs.hh:451:86: error: 'f_info' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive]
>> [ALL ] In file included from /home/peko/source/buildroot/testctng/build/build-toolchain/.build/src/ppl-0.10.2/src/Interval.defs.hh:980:0
>>
>> Yann, Carsten - Any ideas? Googling around seems to suggest that this is
>> related to a host-gcc 4.7.x issue, but people are quite likely to be
>> using that nowadays, so what to do? Build with -fpermissive?
I remember I ran into similar problems with ppl-010.2 while I try to
find a setup for a arm crosscompiler with gcc4.7.1. After choosing
ppl-0.11.2 and setting the switch -fpermissive the build was successful
(but of course with a lot warnings while global settings for LDFLAGS).
> Yes, it requires -fpermissive to build with gcc-4.7.
Right, GCC greater 4.6 are more strict while syntax checking, so without
-fpermissive actual compiler in Debian wheezy will give up. But for me
is setting -fpermisse just a temporaly solution. Newer GCCs will always
give up in such cases and that's correct.
> I am using a Debian squeeze that has a gcc-4.4, so I can't test it.
> I'll try in a wheezy chroot soonish.
No need for that. :-)
Wheezy use the current GCC 4.7.2 and the sources need a patch to correct
the source or the switch -fpermissive.
Because I don't know exactly how to patch the source (I don't have take
a deep look into it) or the Makefile for ppl-0.1x.x inside the
crosstool-ng environment I can't provide some useful right now.
--
Regards
Carsten
prev parent reply other threads:[~2012-12-09 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 19:47 [Buildroot] [PATCH 0/1] Update Crosstool-NG to 1.17.0 Carsten Schoenert
2012-12-03 19:47 ` [Buildroot] [PATCH] package/crosstool-ng: update " Carsten Schoenert
2012-12-04 9:12 ` Thomas Petazzoni
2012-12-04 18:09 ` Yann E. MORIN
2012-12-04 19:35 ` Thomas Petazzoni
2012-12-05 15:30 ` Peter Korsgaard
2012-12-09 20:02 ` Peter Korsgaard
2012-12-09 20:37 ` Yann E. MORIN
2012-12-09 21:18 ` Carsten Schoenert [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=50C50034.7040709@googlemail.com \
--to=c.schoenert@gmail.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.