| 1 |
Am 07.12.2005 12:48 Uhr schrieb "Ned Ludd" unter <solar@g.o>: |
| 2 |
|
| 3 |
> On Wed, 2005-12-07 at 09:07 +0100, Heiko Kopp wrote: |
| 4 |
>> Hello, |
| 5 |
>> |
| 6 |
>> I'm quite new to GNAP but have some experience with gentoo. For a project I |
| 7 |
>> want to integrate the SUN-JRE 1.5 as extension into GNAP using gnap_make. |
| 8 |
>> Unfortunately this package is masked by ~x86. Handling this via an overlay, |
| 9 |
>> I run into another problem. The extension creation fails with a weired error |
| 10 |
>> message: |
| 11 |
>> |
| 12 |
>> /usr/portage/dev-java/sun-jre-bin/sun-jre-bin-1.5.0.05.ebuild: line 69: |
| 13 |
>> ./install.sfx: No such file or directory |
| 14 |
>> |
| 15 |
>> !!! ERROR: dev-java/sun-jre-bin-1.5.0.05 failed. |
| 16 |
>> !!! Function src_unpack, Line 69, Exitcode 127 |
| 17 |
>> !!! (no error message) |
| 18 |
>> !!! If you need support, post the topmost build error, NOT this status |
| 19 |
>> message. |
| 20 |
>> |
| 21 |
>> The ebuild itself fails at line 69 complaining about a missing install.sfx. |
| 22 |
>> Actually this file is created in the ebuild two lines above. |
| 23 |
>> |
| 24 |
>> Can anyone lead me to a hint. If not possible to use this package with the |
| 25 |
>> portage system, the only solution I would think of is to put it directly in |
| 26 |
>> the file system. |
| 27 |
> |
| 28 |
> |
| 29 |
> Note that you are attempting to use a binary package |
| 30 |
> (dev-java/sun-jre-bin) that was probably built and linked against glibc |
| 31 |
> and it's attempting to execute. The no such file or dir error msg is |
| 32 |
> probably the kernel returning the errno msg telling you that it can't |
| 33 |
> find all needed libraries. |
| 34 |
> |
| 35 |
|
| 36 |
I tracked it down a bit. The Ebuild of sun-jre-bin takes the .bin file from |
| 37 |
sun as input. This file is a bash-script with the original binary at the |
| 38 |
end. The ebuild now determines the start of the binary within this file and |
| 39 |
writes only the binary part to the file install.sfx. This file is then |
| 40 |
executed but not found. The shell script simply askes to accept the licence, |
| 41 |
thats why sun builds it this way. |
| 42 |
|
| 43 |
The problem now is, that the underlying catalyst has some problems with |
| 44 |
different change root environments, as the file exists somewhere deep inside |
| 45 |
/tmp/catalyst/tmp .... but obviously cannot be found by the ebuild anymore. |
| 46 |
|
| 47 |
I will add a new question in the gentoo-catalyst mailing list as I suppose |
| 48 |
the problem resides somewhere there. |
| 49 |
|
| 50 |
If anyone as an idea how to fix this issues, I would greatly appreciate it! |
| 51 |
|
| 52 |
Heiko. |
| 53 |
|
| 54 |
|
| 55 |
-- |
| 56 |
gentoo-embedded@g.o mailing list |
Archives