Bug 105875

Summary: missing 'so' suffix on applications
Product: [Fedora] Fedora Reporter: Christian Schaller <uraeus>
Component: automakeAssignee: Daniel Reed <djr>
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-20 04:11:02 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: 100644    
Attachments:
Description Flags
Package that exposes the problem none

Description Christian Schaller 2003-09-28 21:22:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

Description of problem:
Some packages, like musicbrainz or gstreamer-player, seems to build losing the
'so' extension on libraries. This is using the automake 1.7-7 in Severn.
Downgrading to automake-1.6-3 from RH9 makes things work right again. I would
think there is a bug in automake 1.7?

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. download mdk musicbrainz SRPM 
2. fix SPEC to work for RH (just replace %mklibname with a hardcoded one)
3. build package to see issue
    

Actual Results:  all files which where supposed to have a .so* suffix get none
or just the so number as prefix.

Expected Results:  na

Additional info:

attaching the srpm I am using to this bugreport

Comment 1 Christian Schaller 2003-09-28 21:23:04 UTC
Created attachment 94804 [details]
Package that exposes the problem

Comment 2 Jens Petersen 2003-10-03 02:23:10 UTC
When I try to build with automake-1.6.3-5 or automake16, adding:

export AUTOMAKE=automake-1.6
export ACLOCAL=aclocal-1.6

before %configure, I get the same result as with automake-1.7.

This is the first report I have seen of this.  Are you sure it's not
a libmusicbrainz problem?

I recommend asking on the bug-automake or automake lists too.


Comment 3 Daniel Reed 2004-08-20 04:11:02 UTC
This sounds a little too bizarre to have been missed for so long.
Please re-open if you are still able to reproduce. Thanks.