A new version of gcc-defaults with the 'libgcj-dev' patch applied
has just been uploaded to 'unstable'. This will allow to use just
'libgcj-dev' in the Build-Depends.
Ah! Wonderful. When it comes through I'll make the corresponding
change to libreadline-java. (Note that the build-depends
On 05-Mar-25 14:35, Ben Burton wrote:
I took a look at this and I'm uncomfortable with the patch that you've
suggested.
The issue here is that I want to ensure that the installed libgcj-dev
matches the version of gcj that is used. This was in fact the reason
for the latest libreadline-java
Hi,
As a solution, I would suggest to use 'gcj' everywhere, but to introduce
a configure check which tests if 'gcj' and the installed version of
'libgcj-dev' match, i.e. gcj==gcj-3.3/libgcj4-dev, gcj==gcj-3.4/libgcj5-dev
and gcj==gcj-4.0/libgcj6-dev.
But what will you do if the test fails?
On 05-Mar-25 20:08, Ben Burton wrote:
Hi,
As a solution, I would suggest to use 'gcj' everywhere, but to introduce
a configure check which tests if 'gcj' and the installed version of
'libgcj-dev' match, i.e. gcj==gcj-3.3/libgcj4-dev, gcj==gcj-3.4/libgcj5-dev
and
If the test fails, the build should fail with an error message like
The installed libgcj-dev version does not match the installed gcj
version. or similar.
But this then _loses_ the guaranteed success of the build on the regular
architectures. Build-depends aren't just for autobuilders;
On 05-Mar-25 20:47, Ben Burton wrote:
If the test fails, the build should fail with an error message like
The installed libgcj-dev version does not match the installed gcj
version. or similar.
But this then _loses_ the guaranteed success of the build on the regular
architectures.
One solution which comes to my mind would be to make 'libgcj-dev' a real
package like 'gcj' which is provided by 'gcc-defaults' and depends on
the package from the current default gcc version. This would make a
Build-Depends on just 'gcj, libgcj-dev' possible.
Indeed, this would be
On 05-Mar-26 00:02, Ben Burton wrote:
One solution which comes to my mind would be to make 'libgcj-dev' a real
package like 'gcj' which is provided by 'gcc-defaults' and depends on
the package from the current default gcc version. This would make a
Build-Depends on just 'gcj,
On 05-Mar-25 14:43, Andreas Jochens wrote:
On 05-Mar-26 00:02, Ben Burton wrote:
One solution which comes to my mind would be to make 'libgcj-dev' a real
package like 'gcj' which is provided by 'gcc-defaults' and depends on
the package from the current default gcc version. This would
Hi,
Architectures like ppc64 which do not have gcc-3.3 will break when
gcj-3.3 is used instead of gcj.
Please use gcj and libgcj-dev to make porting easier.
I took a look at this and I'm uncomfortable with the patch that you've
suggested.
The issue here is that I want to ensure that the
Package: libreadline-java
Severity: wishlist
Tags: patch
Architectures like ppc64 which do not have gcc-3.3 will break when
gcj-3.3 is used instead of gcj.
Please use gcj and libgcj-dev to make porting easier.
Regards
Andreas Jochens
diff -urN
11 matches
Mail list logo
