On Thu, Jan 05, 2017 at 11:58:07AM +0100, Michael Schwendt wrote:
> On Thu, 5 Jan 2017 00:58:00 +, Richard W.M. Jones wrote:
>
> > It would also be nice if:
> >
> > PYTHON=/usr/bin/python3 %configure
> >
> > didn't (silently) do the wrong thing by default. For a long time we
> > shipped
On Friday, January 6, 2017 3:24:46 PM CET Florian Weimer wrote:
> On 01/06/2017 03:20 PM, Pavel Raiskup wrote:
> > On Friday, January 6, 2017 3:02:22 PM CET Florian Weimer wrote:
> >>> Wouldn't it suffice to put PYTHON= at the end? autotools' configure
> >>> scripts accept such assignments (and
On 01/06/2017 03:20 PM, Pavel Raiskup wrote:
On Friday, January 6, 2017 3:02:22 PM CET Florian Weimer wrote:
Wouldn't it suffice to put PYTHON= at the end? autotools' configure
scripts accept such assignments (and even remember them in
config.status etc).
Indeed, this looks like a reasonable
On Friday, January 6, 2017 3:02:22 PM CET Florian Weimer wrote:
> > Wouldn't it suffice to put PYTHON= at the end? autotools' configure
> > scripts accept such assignments (and even remember them in
> > config.status etc).
>
> Indeed, this looks like a reasonable solution.
Is %configure only for
On 01/06/2017 01:59 PM, Thomas Moschny wrote:
2017-01-05 14:01 GMT+01:00 Florian Weimer :
On 01/05/2017 11:58 AM, Michael Schwendt wrote:
On Thu, 5 Jan 2017 00:58:00 +, Richard W.M. Jones wrote:
It would also be nice if:
PYTHON=/usr/bin/python3 %configure
didn't
2017-01-05 14:01 GMT+01:00 Florian Weimer :
> On 01/05/2017 11:58 AM, Michael Schwendt wrote:
>>
>> On Thu, 5 Jan 2017 00:58:00 +, Richard W.M. Jones wrote:
>>
>>> It would also be nice if:
>>>
>>> PYTHON=/usr/bin/python3 %configure
>>>
>>> didn't (silently) do the wrong
On 01/05/2017 11:58 AM, Michael Schwendt wrote:
On Thu, 5 Jan 2017 00:58:00 +, Richard W.M. Jones wrote:
It would also be nice if:
PYTHON=/usr/bin/python3 %configure
didn't (silently) do the wrong thing by default. For a long time we
shipped a nbdkit-python3 package which was using
On Thu, 5 Jan 2017 00:58:00 +, Richard W.M. Jones wrote:
> It would also be nice if:
>
> PYTHON=/usr/bin/python3 %configure
>
> didn't (silently) do the wrong thing by default. For a long time we
> shipped a nbdkit-python3 package which was using python2, and that was
> found to be the
On Mon, Jan 02, 2017 at 03:10:26PM +0100, Pavel Raiskup wrote:
> On Monday, January 2, 2017 10:56:10 AM CET Florian Weimer wrote:
> > The final values of CFLAGS/LDFLAGS/… are set (as shell variables) by the
> > %configure macro. There is no other immediately obvious way to get
> > those
On Mon, 02 Jan 2017 15:10:26 +0100, Pavel Raiskup wrote:
> >
> > %global %_configure :
> > %configure
> >
> > As a result, %configure tries to run “:” instead of “./configure”, which
> > is a NOP, and only the shell variable initialization remains.
> >
> > Is this the recommend way to
On Monday, January 2, 2017 10:56:10 AM CET Florian Weimer wrote:
> The final values of CFLAGS/LDFLAGS/… are set (as shell variables) by the
> %configure macro. There is no other immediately obvious way to get
> those definitions. This means that if you can't use %configure for some
> reason,
On Mon, Jan 2, 2017 at 10:56 AM, Florian Weimer wrote:
> The final values of CFLAGS/LDFLAGS/… are set (as shell variables) by the
> %configure macro. There is no other immediately obvious way to get those
> definitions. This means that if you can't use %configure for some
The final values of CFLAGS/LDFLAGS/… are set (as shell variables) by the
%configure macro. There is no other immediately obvious way to get
those definitions. This means that if you can't use %configure for some
reason, you are out of luck.
In this situation, this still works:
%global
13 matches
Mail list logo