Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 52632 - emerging syslog-ng-1.6.4 fails when libol-0.3.13 not present
Summary: emerging syslog-ng-1.6.4 fails when libol-0.3.13 not present
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-31 14:57 UTC by Josh Nichols (RETIRED)
Modified: 2004-08-16 19:21 UTC (History)
0 users

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


Attachments
ebuild which solves dependency problem (syslog-ng-1.6.4-r1.ebuild,1.53 KB, application/octet-stream)
2004-05-31 15:10 UTC, Josh Nichols (RETIRED)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Nichols (RETIRED) gentoo-dev 2004-05-31 14:57:56 UTC
emerging syslog-ng-1.6.4 fails when libol-0.3.13 is not present. The ebuild specifies a dependency on libold-0.3.9, but syslog-ng's configure script checks for olibol-0.3.13.

Reproducible: Always
Steps to Reproduce:
1. have libol-0.3.9 installed
2. emerge syslog-ng-1.6.4

Actual Results:  
shinybox syslog-ng # emerge syslog-ng
Calculating dependencies ...done!
>>> emerge (1 of 1) app-admin/syslog-ng-1.6.4 to /
>>> md5 src_uri ;-) syslog-ng-1.6.4.tar.gz
>>> Unpacking source...
>>> Unpacking syslog-ng-1.6.4.tar.gz to /var/tmp/portage/syslog-ng-1.6.4/work
>>> Source unpacked. 
creating cache ./config.cache
--snip--
checking libol version >= 0.3.13... no
configure: error: Required libol version not found

!!! ERROR: app-admin/syslog-ng-1.6.4 failed.
!!! Function econf, Line 365, Exitcode 1
!!! econf failed


Expected Results:  
sucessful emerge
Comment 1 Josh Nichols (RETIRED) gentoo-dev 2004-05-31 15:10:13 UTC
Created attachment 32412 [details]
ebuild which solves dependency problem
Comment 2 Mr. Bones. (RETIRED) gentoo-dev 2004-08-16 19:21:19 UTC
Seems to have been fixed already.