From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Mike Frysinger <vapier@gentoo.org>, Zvi Vered <veredz72@gmail.com>
Subject: Re: crosstool 1.13.1: ncurses stage hangs
Date: Sun, 20 Nov 2011 14:32:00 -0000 [thread overview]
Message-ID: <201111201532.08788.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <201111182256.14149.vapier@gentoo.org>
Zvi, Mike,
On Saturday 19 November 2011 04:56:13 Mike Frysinger wrote:
> On Friday 18 November 2011 22:50:59 Zvi Vered wrote:
> > [ALL ] Running /usr/bin/tic
>
> terrible idea. crosstool needs to build up a local one and run that.
That's already the case. The issue was that ncurses-5.9 does not look in
$PATH for the tic to run, and uses, in order:
${TIC_PATH}
/usr/bin/tic
Yes, that last one is hard-coded! ncurses-5.8 did behave correctly in this
regard.
And since I upgraded my machie to a newer distro, I did not catch the
problem.
But it is now fixed in the default branch:
http://crosstool-ng.org/hg/crosstool-ng/rev/bd17cca444ae
I'll back-port this fix to the 1.13 branch, and will probably put out a
release soonish. In the meantime, you just need to apply this patch to
your local sources.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2011-11-20 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 3:51 Zvi Vered
2011-11-19 3:56 ` Mike Frysinger
2011-11-20 14:32 ` Yann E. MORIN [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=201111201532.08788.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=vapier@gentoo.org \
--cc=veredz72@gmail.com \
/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).