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 gcj==gcj-4.0/libgcj6-dev. > > But what will you do if the test fails? The problem is not just at the
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. > debian/rules level, it goes all the way back to the build-depends level. > Build-depending on gcj will give you a precise version of gcj (the > default), whereas build-depending on libgcj-dev gives you no guarantee > on what version of libgcj-dev you get. > > The only solution I can see at this stage is to build-depend on a > specific version of libgcj-dev (e.g., libgcj4-dev). And at this point > you then have to build-depend on the specific version of gcj to match, > and we're back at the current state of affairs. Build-Depends on 'libgcj4-dev | libgcj-dev' would cause autobuilders to install 'libgcj4-dev' which is correct. On the other hand, the Build-Depends can also be fulfilled by e.g. 'libgcj6-dev' and the package would compile with that if the default gcj is gcj-4.0. That way the package does not have to be changed if the default gcj is different. Regards Andreas Jochens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
