[Rpm-maint] Re: %configure assuming in-source-tree builds

Vasile Gaburici vgaburici at gmail.com
Mon Aug 11 10:22:35 UTC 2008

Poppler's spec does this:

pushd %{name}-%{version}
# despair
sed -i s/qt3/qt-3.3/g configure
%configure \
  --disable-static \
  --enable-cairo-output \
  --enable-poppler-qt \
  --enable-poppler-qt4 \
make %{?_smp_mflags}

Is this not good enough for some reason?

On Mon, Aug 11, 2008 at 1:18 PM, Stepan Kasal <skasal at redhat.com> wrote:
> Hello,
> On Mon, Jun 23, 2008 at 10:39:49AM -0400, Peter Jones wrote:
>>> Michel Salim wrote:
>>>> Hi all,
>>>> Some upstream developers recommend that their software (thinking of LLVM
>>>> and PLT Scheme, but there must be others) *not* be configured and built
>>>> at the top-level source directory (typically recommending using build/,
>>>> object/ or some such).
>>>> When this is needed, currently the Fedora packager has to revert to
>>>> calling the configure script directly, foregoing the %configure macro,
>>>> and copying as much of the configure settings by hand. Would it be a
>>>> desirable feature to, say, be able to declare
>>>> %define configure_relative_path
>> I'd really rather see something like [this] suggestion.
> Agreed.  Filed as http://bugzilla.redhat.com/458644
> [This is suitable to be submitted upstream, but rpm.org does not have
> a bug tracker, it features only lists, and I did not care to
> subscribe before cc'ing this mail, so I guess my chanced to get
> heared there are low.  They read fedora bugzilla, though.  ;-) ]
> Stepan Kasal
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list

More information about the Rpm-maint mailing list