Hot Diggety! Pietro Leone was rumored to have written:
> Emerging and compiling db-4.0.14-r2 (for vlc) I obtain this output, why
> it does not like my jar executable? The directory in which jar is IS
> into the PATH env variable, but the bash does not view it and so does
> make.
>
> [snip]
> checking for gcj... gcj -C
> checking if gcj -C works... yes
> checking for jar... no
> configure: error: no acceptable jar program found in $PATH
>
> !!! ERROR: sys-libs/db-4.0.14-r2 failed.
> !!! Function src_compile, Line 64, Exitcode 1
> !!! (no error message)
>
> Someone can explain me this?
I had to hack the .ebuild file (one line change) to work around that.
I edited /usr/portage/sys-libs/db/db-4.0.14-r2.ebuild at line 54 to
change from:
export PATH=`dirname ${JAVAC}`:${PATH}
to:
export PATH=/path/to/jarbinary:${PATH}
For example, if your jar was in /opt/blackdown-jdk-1.4.1/bin then you'd
change the line to:
export PATH=/opt/blackdown-jdk-1.4.1/bin:${PATH}
Then:
# emerge /usr/portage/sys-libs/db/db-4.0.14-r2.ebuild
(to build+install it)
The next rsync will back out the changes but that's ok - you only need
it for one time. That's the workaround I used as a temporary measure since
I'm sure it'd be fixed soon.
Not sure why it'd pop up because JAVAC environment variable is present and
pointing to the javac binary, and dirname works fine on the command line.
-Dan
--
[EMAIL PROTECTED] mailing list
