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 115989

Summary: Does not build
Product: [Fedora] Fedora Reporter: Miloslav Trmac <mitr>
Component: memprofAssignee: Owen Taylor <otaylor>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-24 19:15:56 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:

Description Miloslav Trmac 2004-02-17 14:47:48 UTC
Description of problem:
SSIA, build fails with
File not found: File not found: 

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

Additional info:
@@ -35,7 +35,7 @@
 autoheader
 autoconf
 %configure
-make
+make LIBTOOL=/usr/bin/libtool
                                                                     
          
 %install
 rm -rf $RPM_BUILD_ROOT

Comment 1 Miloslav Trmac 2004-02-17 14:48:09 UTC
*** Bug 107477 has been marked as a duplicate of this bug. ***

Comment 2 Owen Taylor 2004-02-17 16:02:34 UTC
Note that using LIBTOOL=/usr/bin/libtool is not legal according
to the libtool authors and produces strange build problems and 
failures. The right solution to these types of issues is usually 
to rerun libtoolize and autoconf.

Comment 3 Owen Taylor 2004-11-24 19:15:56 UTC
If redhat bugzilla had an INCOMPLETE resolution like GNOME bugzilla,
I'd use that. I don't think there is sufficient information here
to figure out what is going on, and I have confidence that next
time I do a rebuild I'll fix the problem one way or the other if
it is still occurring.