Bug 123299 - BuildRequires in libtool to gcc-c++ and libstdc++-devel missing
Summary: BuildRequires in libtool to gcc-c++ and libstdc++-devel missing
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libtool
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-16 11:18 UTC by Robert Scheck
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: 1.5.6-4
Clone Of:
Environment:
Last Closed: 2004-07-15 13:29:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2004-05-16 11:18:39 UTC
Description of problem:
A libtool rebuilding fails always at the end of the 98 tests and says
that there were errors at three tests: "tagdemo-make.test"

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

How reproducible:
Everytime

Steps to Reproduce:
1. Have no gcc-c++ and no libstdc++-devel installed
2. Rebuild libtool
3. Get the error described above
  
Actual results:
--- libtool.spec        2004-04-12 03:50:07.000000000 +0200
+++ libtool.spec.rsc    2004-05-16 13:13:19.000000000 +0200
@@ -22,7 +22,7 @@
 #Patch16: libtool-1.5-AC_PROG_LD_GNU-quote-v-97608.patch
 #Patch17: libtool-1.5-nostdlib.patch
 PreReq: /sbin/install-info, autoconf, automake >= 1.4p1, m4, perl
-BuildRequires: autoconf automake
+BuildRequires: autoconf, automake, gcc-c++, libstdc++-devel
 Requires: libtool-libs = %{version}-%{release}, mktemp
 BuildRoot: %{_tmppath}/%{name}-root

Expected results:
gcc-c++ and libstdc++-devel as BuildRequires

Additional info:
I know that gcc-c++ and libstdc++-devel normally are the default, but
if you get this error at the top you're searching for it hours and
finding that simple result at least...

Comment 1 Jens Petersen 2004-05-17 04:38:43 UTC
Thanks for the report: adding gcc-g77 and ghc-gcj too in next build.

Comment 2 Robert Scheck 2004-07-15 13:29:53 UTC
Thank you Jens for fixing it :)


Note You need to log in before you can comment on or make changes to this bug.