Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 449534
Summary: | FTBFS libapreq2-2.09-0.15.rc2.fc9 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | FTBFS <ftbfs> | ||||||||||||
Component: | libapreq2 | Assignee: | Bojan Smojver <bojan> | ||||||||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | high | Docs Contact: | |||||||||||||
Priority: | high | ||||||||||||||
Version: | rawhide | ||||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | All | ||||||||||||||
OS: | Linux | ||||||||||||||
URL: | http://linux.dell.com/files/fedora/FixBuildRequires/mock-results-core/ | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2008-06-05 01:09:09 UTC | Type: | --- | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Bug Depends On: | |||||||||||||||
Bug Blocks: | 440169 | ||||||||||||||
Attachments: |
|
Description
FTBFS
2008-06-02 20:25:55 UTC
Created attachment 307783 [details] root.log.bz2 root.log for i386 Created attachment 307784 [details] build.log.bz2 build.log for i386 Created attachment 307785 [details] root.log.bz2 root.log for x86_64 Created attachment 307786 [details] build.log.bz2 build.log for x86_64 Looking at the build log: ----------------------------------- /etc/profile: line 38: /bin/hostname: No such file or directory sh: /usr/sbin/apxs: No such file or directory cat: /.mmn : No such file or directory ----------------------------------- Without apxs, this build has zero chance of succeeding. The package spec file correctly includes: ----------------------------------- BuildRequires: httpd-devel >= 2.0.48 ----------------------------------- Which in turn delivers /usr/sbin/apxs. So, I don't know what's going on here. Maybe we don't have permission to look into /usr/sbin or something in the build system? I don't think that's the problem. It's something to do with glue: Making all in glue make[1]: Entering directory `/builddir/build/BUILD/libapreq2-2.09/glue' cd perl; perl Makefile.PL -apxs /usr/sbin/apxs INSTALLDIRS=vendor Can't find apache include directory at Makefile.PL line 66. make[1]: *** [perl/Makefile] Error 9 make[1]: Leaving directory `/builddir/build/BUILD/libapreq2-2.09/glue' make: *** [all-recursive] Error 1 The "Can't find apache include directory at Makefile.PL line 66." is the result of APACHE2_INCLUDES not being present in config.status: ---------------------------- slurp my $config => "$base_dir/config.status"; $config =~ /^s,\@APACHE2_INCLUDES\@,([^,]+)/m or die "Can't find apache include directory"; ---------------------------- And this line of config.status is supposed to be written out by configure, using this in acinclude.m4: ---------------------------- APACHE2_INCLUDES=-I`$APACHE2_APXS -q INCLUDEDIR` [...] AC_SUBST(APACHE2_INCLUDES) ---------------------------- I can see this in my config.status on my F9 machine. Can you attach the config.status file from that run? Created attachment 308242 [details]
config.status
Thank Matt. Looks like the format of config.status changed: new: S["APACHE2_INCLUDES"]="-I/usr/include/httpd" old: s,@APACHE2_INCLUDES@,|#_!!_#|-I/home/groups/devel/run/apache/include,g I'm guessing the version of autoconf delivered this change or something... This has been fixed in 0.17.rc2. Fix for this has been committed upstream as well. |