[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#370518: marked as done (placing jni.h in versioned subdirectory makes no sense)



Your message dated Mon, 5 Jun 2006 21:14:53 +0200
with message-id <17540.33453.403833.967468@gargle.gargle.HOWL>
and subject line Bug#370518: placing jni.h in versioned subdirectory makes no sense
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: libgcj7-dev
Version: 4.1.0-2j1
Severity: grave

This package installs jni.h in /usr/lib/gcc/i486-linux-gnu/4.1.1/include/.
This only works if you happen to use gcc 4.1.1 to compile the C program
you're dealing with, but my gcc thinks it's version 4.0.4:

$ gcc -print-search-dirs
install: /usr/lib/gcc/i486-linux-gnu/4.0.4/
programs: =/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/:/usr/libexec/gcc/i486-linux-gnu/4.0.4/:/usr/libexec/gcc/i486-linux-gnu/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/bin/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/bin/
libraries: =/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/lib/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/lib/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../:/lib/i486-linux-gnu/4.0.4/:/lib/:/usr/lib/i486-linux-gnu/4.0.4/:/usr/lib/

Since gcj-x.y and gcc-x.y are different source packages, you are bound
to have this sort of descrepancy once in a while.

In order to allow packages to use the JNI interface without breaking
every so often, the header files need to be placed in a directory where
every compiler can find them.


--- End Message ---
--- Begin Message ---
rejecting this report. Either use -I/usr/lib/jvm/java-gcj/include or
-I$(dirname $(gcj -print-file-name=include/jni.h))

See as well
http://lists.debian.org/debian-devel-announce/2006/05/msg00008.html

Peter Eisentraut writes:
> Package: libgcj7-dev
> Version: 4.1.0-2j1
> Severity: grave
> 
> This package installs jni.h in /usr/lib/gcc/i486-linux-gnu/4.1.1/include/.
> This only works if you happen to use gcc 4.1.1 to compile the C program
> you're dealing with, but my gcc thinks it's version 4.0.4:
> 
> $ gcc -print-search-dirs
> install: /usr/lib/gcc/i486-linux-gnu/4.0.4/
> programs: =/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/:/usr/libexec/gcc/i486-linux-gnu/4.0.4/:/usr/libexec/gcc/i486-linux-gnu/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/bin/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/bin/
> libraries: =/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/lib/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/lib/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../:/lib/i486-linux-gnu/4.0.4/:/lib/:/usr/lib/i486-linux-gnu/4.0.4/:/usr/lib/
> 
> Since gcj-x.y and gcc-x.y are different source packages, you are bound
> to have this sort of descrepancy once in a while.
> 
> In order to allow packages to use the JNI interface without breaking
> every so often, the header files need to be placed in a directory where
> every compiler can find them.
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

--- End Message ---

Reply to: