Commit Graph

6 Commits

Author SHA1 Message Date
Mark Wielaard 3d4db6f99f Define AM_CFLAGS inside the Makefile.am files themselves.
Trying to include AM_CFLAGS through a configure generated rpm.am file
doesn't really work because at the time automake runs configure doesn't
exist yet to process rpm.am.in. Just define the AM_CFLAGS substitution
inside the Makefile.am files themselves.

Rename rpm.am.in back to rpm.am.

Signed-off-by: Mark Wielaard <mjw@redhat.com>
2016-12-09 11:35:38 +02:00
Panu Matilainen bd3eb21336 Stop messing with CFLAGS from configure
CFLAGS is a user variable that software is supposed to honor but not
touch, that's what AM_CFLAGS and friends are for. rpm.am is
included by all our makefiles so that's a handy place to set defaults
centrally, do so by AC_SUBST'ing the rpm cflags into AM_CFLAGS there.
2016-12-08 12:53:54 +02:00
Florian Festi 1e3dd48f5a Bump library version 2015-07-24 10:08:59 +02:00
Panu Matilainen aa2765a872 Bump library versions to match reality
- Rpm 4.11.2 is at 5:1:2. We've tonne of new APIs but none removed
  or changed incompatibly (I think, knock wood...) so no need
  for full soname bump, this brings us to libtool version 6:0:3
  in preparation for rpm 4.12
2014-06-25 13:34:34 +03:00
Panu Matilainen 3f2f483515 Use unified libtool version for all our libraries
- Our libraries are in reality so interdependent that its not even
  possible to use them independently of others, so having them
  all follow sort of independent versioning information just doesn't
  make any sense and is a PITA everytime I need to touch the data.
- This causes librpmsign soname bump with no good reason so its
  probably "evil" and all ... so sue me, its not as if anybody
  is actually using this library outside rpm itself.
2014-06-25 13:21:00 +03:00
Ralf Corsépius c544a9579a New. 2007-09-05 10:39:57 +02:00