GCJ and $PREFIX/include revisited

Mon Dec 15 03:02:00 GMT 2003

On Tue, 6 May 2003, Tom Tromey wrote:
>> Currently GCJ puts a lot of headers directly in $PREFIX/include:
>>>> ffi.h
>> ffi_mips.h
>> fficonfig.h
>> gc.h
>> gc_backptr.h
>> gc_cpp.h
>> gc_local_alloc.h
>> gc_pthread_redirects.h
> I'm not sure we should be installing these headers at all.
> libffi is arguable, given that the independent libffi seems pretty
> dead.

I know that this is an old one, and indeed the situation has improved
quite a bit, but still there seems work to do:
 drwxr-xr-x 3 pfeifer staff 512 Dec 14 04:58 c++
 -rw-r--r-- 1 pfeifer staff 9092 Dec 14 04:59 ffi.h
 drwxr-xr-x 2 pfeifer staff 512 Dec 14 04:59 gcj
 drwxr-xr-x 7 pfeifer staff 512 Dec 14 05:02 gnu
 drwxr-xr-x 15 pfeifer staff 512 Dec 14 05:01 java
 drwxr-xr-x 10 pfeifer staff 512 Dec 14 05:02 javax
 -rw-r--r-- 1 pfeifer staff 6870 Dec 14 04:59 jvmpi.h
The c++ headers are now nicely versioned, in c++/3.4/, but the java
headers still are put directly into $PREFIX. How about doing something
like java/3.4 or gcj/3.4 in parallel to c++?
And do we really need ffi.h and jvmpi.h there?
(This is PR7305, and it would be really nice to fix this for GCC 3.4.
in fact, it is, somehow, a regression against earlier versions of GCC.)
Gerald
-- 
Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/