syslog-ng version 3.2.4-1 failed to build on armel

Bug #791237 reported by Ricardo Salveti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
syslog-ng (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

syslog-ng version 3.2.4-1 failed to build on armel
Link to failed build: https://launchpad.net/ubuntu/+source/syslog-ng/3.2.4-1/+build/2513300

Direct link to the build log: https://launchpad.net/ubuntu/+source/syslog-ng/3.2.4-1/+build/2513300/+files/buildlog_ubuntu-oneiric-armel.syslog-ng_3.2.4-1_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 714 lines into the build log:

checking for strcasestr... yes
checking for memrchr... yes
checking for EVTLOG... no
configure: error: Package requirements (eventlog >= 0.2.12) were not met:

Requested 'eventlog >= 0.2.12' but version of EventLog is 0.2.7

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables EVTLOG_CFLAGS
and EVTLOG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
make: *** [configure-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110519-0742
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/syslog-ng-3.2.4

Revision history for this message
Riku Voipio (riku-voipio) wrote :

This is a bug in the package. The build-dependency of libevtlog-dev should be versioned.

-Build-Depends: quilt, debhelper (>= 5), libnet1-dev, libevtlog-dev, libssl-dev,
+Build-Depends: quilt, debhelper (>= 5), libnet1-dev, libevtlog-dev (>=0.2.12), libssl-dev,

Revision history for this message
Ricardo Salveti (rsalveti) wrote :

This bug happens because eventlog 0.2.12-1 is also FTBFS: bug 791265

Changed in syslog-ng (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.