Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 410697 - gnustep-libs/dbuskit-0.1 fails to configure: ObjectiveC2/runtime.h: No such file or directory
Summary: gnustep-libs/dbuskit-0.1 fails to configure: ObjectiveC2/runtime.h: No such f...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Gnustep project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 410601
  Show dependency tree
 
Reported: 2012-04-03 19:34 UTC by Agostino Sarubbo
Modified: 2013-07-05 16:29 UTC (History)
0 users

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 Agostino Sarubbo gentoo-dev 2012-04-03 19:34:27 UTC
Sorry If I'm unable to paste complete build log:

from build.log

checking for objc/runtime.h... no
configure: error: "could not find runtime.h. DBusKit requires gnustep-base >=1.20."

from config.log: 

conftest.m:21:33: fatal error: ObjectiveC2/runtime.h: No such file or directory
compilation terminated.

test ~ # ls /usr/include/ObjectiveC2/ -R
/usr/include/ObjectiveC2/:
objc

/usr/include/ObjectiveC2/objc:
Availability.h  blocks_runtime.h  capabilities.h  runtime.h


so the configure should search ObjectiveC2/objc/runtime.h
Comment 1 Bernard Cafarelli gentoo-dev 2012-04-03 20:52:45 UTC
I probably had a leftover /usr/include/objc from my testing, thanks for spotting this one! Fixed path in configure.ac (the ebuild already run eautoreconf for another patch)
Comment 2 tinyplasticgreyknight 2013-07-04 22:24:25 UTC
I think this has regressed in dbuskit-0.1.1.ebuild.  I'm seeing a similar error and I notice that the ebuild has removed the sed filter on configure.ac
Comment 3 Bernard Cafarelli gentoo-dev 2013-07-05 16:29:43 UTC
Indeed, this was removed at the same time as the configure patch, but it was not the same bug. Thanks for the report, I have reintroduced the fix in 0.1.1