On a new install with profile `hardened/x86/2.6'. I'm finding that
ksh will not emerge successfully. The closing error is not very
enlightening, at least not to me:
* Messages for package app-shells/ksh-93.20040229:
* ERROR: app-shells/ksh-93.20040229 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ksh-93.20040229.ebuild, line 51: Called die
* The specific snippet of code:
* cd ${S}; ./bin/package only make ast-ksh CC="$(tc-getCC)" || die
* The die message:
* (no error message)
In the days before ksh93 (circa 2003/4) was an ebuild (or maybe I just
didn't know it was) it was a right pain to build and install it by
hand.
I've never understood the unusual build process of the KORN tools and
I see emerge go thru truly massive work to build it too. So the
chances of me finding what went wrong is just about non-existent.
Near as I can tell the closest thing to a similar bug that got
reported was in 2004 and it appears the only helpfull part of that was
setting `nls' as one of the USE items.
emerge is using `nls' and `-static' here. `nls' enables native
language support using gettext which I do have installed, also with
`nls' use set.
==========
I've just noticed something by running `emerge -vDp ksh', it wants a
different compiler than I have installed.
gcc-4.1.1-r3 got installed when I started building up this new system.
ksh apparently wants:
[ebuild NS ] sys-devel/gcc-3.4.6-r2 USE="hardened nls (-altivec)
-bootstrap -boundschecking -build -d -doc -fortran -gcj -gtk -ip28
-ip32r10k -multilib -multislot (-n32) (-n64) -nocxx -nopie -nossp
-objc -test -vanilla"
as a `Deep' dependancy.
Will I be really messing up my new system if I install two version of
gcc? And secondly how does the right one get used for ksh?
I can live without ksh of course but I do have quite a few homemade
scripts that depend on ksh. Many of them will need some recoding even
to use pdksh as I recall.
--
[EMAIL PROTECTED] mailing list
