From: Simon Gornall <sgornall@apple.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: crossgcc@sourceware.org, Trevor Woerner <twoerner@gmail.com>
Subject: Re: Can't compile crosstool-ng-1.15.2 on OpenSuse Linux
Date: Sun, 22 Jul 2012 16:15:00 -0000 [thread overview]
Message-ID: <AD1C0790-FE7E-4741-A22E-210E53FEDED1@apple.com> (raw)
In-Reply-To: <201207221637.07356.yann.morin.1998@free.fr>
On 22 Jul 2012, at 07:37, Yann E. MORIN wrote:
> Trevor, Simon, All,
>
> On Friday 06 July 2012 15:40:01 Trevor Woerner wrote:
>> On Thu, Jul 5, 2012 at 7:17 PM, Simon Gornall <sgornall@apple.com> wrote:
>>> Thanks for the quick response [grin] I didn't know menu.h was part of
>>> ncurses, so I've now made sure it's there
>>> but I still get the same
>>
>> Does the following help?
>> http://sourceware.org/ml/crossgcc/2012-02/msg00002.html
>
> Unfortunately, that patch breaks on other distros (eg. Debian squeeze).
>
> IIRC, there was another solution: install the non-wide-char ncurses devel
> package.
In which case, doing what I originally did, and adding "-I/usr/include/ncurses" to the CFLAGS declaration inside the Makefile in kconfig/ might seem to be the way to go. Adding ncurses itself didn't help because they're installed inside a container directory in /usr/include, but appending the above -I flag ought to be innocuous on non-suse systems (right?) and it lets suse-linux compile cleanly.
Cheers
Simon
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-07-22 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 21:07 Simon Gornall
2012-07-05 22:51 ` Samuel Martin
2012-07-05 23:18 ` Simon Gornall
2012-07-06 14:07 ` Trevor Woerner
2012-07-09 1:35 ` Simon Gornall
2012-07-22 14:42 ` Yann E. MORIN
2012-07-22 16:15 ` Simon Gornall [this message]
2012-07-31 21:20 ` Yann E. MORIN
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=AD1C0790-FE7E-4741-A22E-210E53FEDED1@apple.com \
--to=sgornall@apple.com \
--cc=crossgcc@sourceware.org \
--cc=twoerner@gmail.com \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).