Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 23576 - tinycobol does not build with db4
Summary: tinycobol does not build with db4
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: db4
  Show dependency tree
 
Reported: 2003-06-27 04:28 UTC by Paul de Vrieze (RETIRED)
Modified: 2003-07-08 00:12 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul de Vrieze (RETIRED) gentoo-dev 2003-06-27 04:28:36 UTC
Tinycobold has a hardcoded include statement for /usr/include/db3, while in its
DEPEND statement it specifies that it can run with >=db3
Comment 1 Patrick Kursawe (RETIRED) gentoo-dev 2003-06-27 04:45:22 UTC
Since I don't feel qualified to test it with db4, I just changed the dependency.
Comment 2 Paul de Vrieze (RETIRED) gentoo-dev 2003-06-27 05:03:40 UTC
It still does not compile when db4 is installed as it only looks for db3 and db, while it should look for db-3
Comment 3 Patrick Kursawe (RETIRED) gentoo-dev 2003-06-27 05:50:56 UTC
Sorry, that wasn't clear from your first report. Maybe I'll check it next monday, still have some work to do with a much lower "nice" value.
Comment 4 Paul de Vrieze (RETIRED) gentoo-dev 2003-06-27 05:59:26 UTC
I did not know that either until I checked myself. It is not that tinycobol is a very important package.
Comment 5 Patrick Kursawe (RETIRED) gentoo-dev 2003-07-07 23:50:59 UTC
The configure script looks like it also checks for db4... investigating.
Comment 6 Patrick Kursawe (RETIRED) gentoo-dev 2003-07-08 00:12:22 UTC
Silly me!
For some reason I put
1.1          (phosphan 12-May-03):      econf --with-libdb=3 
in the ebuild and then we wonder why it uses db3....
I have not the slightest idea any more why it was there, it seems to work without that and the package is still ~x86, so I just removed it.
Should be fixed.