Gary Jefferson wrote:
> On Sep 20, 10:43 pm, Gary Jefferson <[EMAIL PROTECTED]>
> wrote:
>> I've got a python extension that comes with its own standard autoconf/
>> automake system, and I can "python setup.py build" just fine with it
>> as long as I have previously done "./configure" in that direc
Gary Jefferson wrote:
> On Sep 20, 10:43 pm, Gary Jefferson <[EMAIL PROTECTED]>
> wrote:
>> I've got a python extension that comes with its own standard autoconf/
>> automake system, and I can "python setup.py build" just fine with it
>> as long as I have previously done "./configure" in that direc
On Sep 20, 10:43 pm, Gary Jefferson <[EMAIL PROTECTED]>
wrote:
> I've got a python extension that comes with its own standard autoconf/
> automake system, and I can "python setup.py build" just fine with it
> as long as I have previously done "./configure" in that directory.
>
> However, 'python se
I've got a python extension that comes with its own standard autoconf/
automake system, and I can "python setup.py build" just fine with it
as long as I have previously done "./configure" in that directory.
However, 'python setup.py bdist_rpm' can't hope to have done './
configure' first, as it un
