crosstool 1.13.1: ncurses stage hangs

crosstool 1.13.1: ncurses stage hangs

[Zvi Vered]

Hello,

I'm trying to build a toolchain for i686-nptl-linux-gnu using
crosstool 1.13.1 under centos 5.7.

The build is OK till it get to the "ncurses" stage.

In this point the build hangs forever (I stopped after 3 hours).

This is last fragment in build.log:

[ALL  ]    cd misc && /usr/bin/make -w DESTDIR="" install
[ALL  ]    make[2]: Entering directory
`/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/i686-nptl-linux-gnu/build/build-ncurses/misc'
[ALL  ]    mkdir -p
/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/i686-nptl-linux-gnu/build/static-target/share
[ALL  ]    mkdir -p
/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/i686-nptl-linux-gnu/build/static-target/share/tabset
[ALL  ]    DESTDIR=
	prefix=/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/i686-nptl-linux-gnu/build/static-target
	exec_prefix=/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/i686-nptl-linux-gnu/build/static-target
	bindir=/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/i686-nptl-linux-gnu/build/static-target/bin
	top_srcdir=/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/src/ncurses-5.9
	srcdir=/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/src/ncurses-5.9/misc
	datadir=/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/i686-nptl-linux-gnu/build/static-target/share
	ticdir=/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/i686-nptl-linux-gnu/build/static-target/share/terminfo
	source=terminfo.tmp 	cross_compiling=yes 	/bin/sh ./run_tic.sh
[ALL  ]    ** Building terminfo database, please wait...
[ALL  ]    Running /usr/bin/tic to install
/home/zvivered/toolchain/ct-ng-1.13.1/bin/.build/i686-nptl-linux-gnu/build/static-target/share/terminfo
...
[ALL  ]
[ALL  ]    	You may see messages regarding extended capabilities, e.g., AX.
[ALL  ]    	These are extended terminal capabilities which are compiled
[ALL  ]    	using
[ALL  ]    		tic -x
[ALL  ]    	If you have ncurses 4.2 applications, you should read the INSTALL
[ALL  ]    	document, and install the terminfo without the -x option.
[ALL  ]

What toolchain utlity uses ncurses ?

Thanks,
Zvika.

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: crosstool 1.13.1: ncurses stage hangs

[Mike Frysinger]

[-- Attachment #1: Type: Text/Plain, Size: 164 bytes --]

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.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: crosstool 1.13.1: ncurses stage hangs

[Yann E. MORIN]

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