| 1 |
On a new install with profile `hardened/x86/2.6'. I'm finding that |
| 2 |
ksh will not emerge successfully. The closing error is not very |
| 3 |
enlightening, at least not to me: |
| 4 |
|
| 5 |
* Messages for package app-shells/ksh-93.20040229: |
| 6 |
|
| 7 |
* ERROR: app-shells/ksh-93.20040229 failed. |
| 8 |
* Call stack: |
| 9 |
* ebuild.sh, line 1701: Called dyn_compile |
| 10 |
* ebuild.sh, line 1039: Called qa_call 'src_compile' |
| 11 |
* ebuild.sh, line 44: Called src_compile |
| 12 |
* ksh-93.20040229.ebuild, line 51: Called die |
| 13 |
* The specific snippet of code: |
| 14 |
* cd ${S}; ./bin/package only make ast-ksh CC="$(tc-getCC)" || die |
| 15 |
* The die message: |
| 16 |
* (no error message) |
| 17 |
|
| 18 |
In the days before ksh93 (circa 2003/4) was an ebuild (or maybe I just |
| 19 |
didn't know it was) it was a right pain to build and install it by |
| 20 |
hand. |
| 21 |
|
| 22 |
I've never understood the unusual build process of the KORN tools and |
| 23 |
I see emerge go thru truly massive work to build it too. So the |
| 24 |
chances of me finding what went wrong is just about non-existent. |
| 25 |
|
| 26 |
Near as I can tell the closest thing to a similar bug that got |
| 27 |
reported was in 2004 and it appears the only helpfull part of that was |
| 28 |
setting `nls' as one of the USE items. |
| 29 |
|
| 30 |
emerge is using `nls' and `-static' here. `nls' enables native |
| 31 |
language support using gettext which I do have installed, also with |
| 32 |
`nls' use set. |
| 33 |
|
| 34 |
========== |
| 35 |
|
| 36 |
I've just noticed something by running `emerge -vDp ksh', it wants a |
| 37 |
different compiler than I have installed. |
| 38 |
|
| 39 |
gcc-4.1.1-r3 got installed when I started building up this new system. |
| 40 |
|
| 41 |
ksh apparently wants: |
| 42 |
|
| 43 |
[ebuild NS ] sys-devel/gcc-3.4.6-r2 USE="hardened nls (-altivec) |
| 44 |
-bootstrap -boundschecking -build -d -doc -fortran -gcj -gtk -ip28 |
| 45 |
-ip32r10k -multilib -multislot (-n32) (-n64) -nocxx -nopie -nossp |
| 46 |
-objc -test -vanilla" |
| 47 |
|
| 48 |
as a `Deep' dependancy. |
| 49 |
|
| 50 |
Will I be really messing up my new system if I install two version of |
| 51 |
gcc? And secondly how does the right one get used for ksh? |
| 52 |
|
| 53 |
I can live without ksh of course but I do have quite a few homemade |
| 54 |
scripts that depend on ksh. Many of them will need some recoding even |
| 55 |
to use pdksh as I recall. |
| 56 |
|
| 57 |
-- |
| 58 |
gentoo-user@g.o mailing list |
Archives