Bug 56189 - %GNUconfigure macro broken
Summary: %GNUconfigure macro broken
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-13 19:03 UTC by Enrico Scholz
Modified: 2008-05-01 15:38 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-11-13 19:03:19 UTC


Attachments (Terms of Use)

Description Enrico Scholz 2001-11-13 19:03:14 UTC
Description of Problem:

The %GNUconfigure macro is broken in several aspects:
- it does not set CXXFLAGS
- it sets LDFLAGS to an empty string; with recent autotools
(autoconf-2.52-3, automake-1.5-1) it fails to detect the C++ compiler,
because it tries to execute "g++ '' conftest.cc" in a autoconf-test. There
'' is the value of $LDFLAGS and g++ won't find this file.
- adding additional flags to ./configure is not intuitive (you have to
execute %{GNUconfigure -- --extra-flags=...}). A solution could be a
definition of %GNUconfigure as a sh-function and calling this at the end:

| % define GNUconfigure(MCs:)
|   function __rpm_gnuconfigure {
|      ... body ...
|      ./configure ... "$@"
|      ...
|   }; __rpm_gnuconfigure

- the filename "configure.in" (used in some tests) is deprecated in recent
autotools; configure.ac is recommended now

- the whole libtoolize/autoheader/aclocal/autoconf stuff can be replaced by
a simple "autoreconf -i"


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

rpm-4.0.3-1.04

Comment 1 Jeff Johnson 2001-11-15 23:42:01 UTC
Nod. Meanwhile, %GNUconfigure is hardly used, and not worth the
effort of fixing. Don't use it is the message.


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