On 7/20/06, David Lee <[EMAIL PROTECTED]> wrote:
On Thu, 20 Jul 2006, Andrew Beekhof wrote:
> On 7/20/06, David Lee <[EMAIL PROTECTED]> wrote:
> > On Thu, 20 Jul 2006, Andrew Beekhof wrote:
> >
> > > I'm going to have to revert this... it prevents the .py files from
> > > being regenerated when the .py.in ones change
> >
> > Hmmm... So it does.
> >
> > But using "_PYTHON" feels like the right general approach to pursue. So
> > either I've overlooked a subtlety in following that (my bug), or there
> > might be an automake problem (automake bug). Either way, it would be nice
> > to understand a little more about this problem before (or at least in
> > parallel to) simply reverting it.
> >
> > If it's our (my!) bug, we can fix it.
> >
> > If it's an automake bug, we are honour-bound to report it back to the
> > automake maintainers. (And we (heartbeat) might then need to revert my
> > patch as a local "necessary evil"(*) expedient workaround.)
>
> I think its a conceptual difference.
>
> _SCRIPT seems to mean generate x.py from x.py.in
> whereas _PYTHON seems to mean generate x.pyc from x.py
Yes. A little local test seems to support that.
> my main problem with it is that with _PYTHON, I cant run CTS _at_all_.
> so i think we must revert it until an alternate work-around for the
> change you made is found.
Fair enough: it sounds as if reversion is necessary for the moment.
Let's revert. (Can you do the reversion? Let me know if you want me to
do it.)
I can do it
Meanwhile, I've taken a look at the generated Makefiles and think I see
_why_ it failing as you described. (But that doesn't explain why it's
being generated like that.)
I've attempted a local workaround. It looks functionally OK, but has the
feel of digging deeper into a nasty hole that I shouldn't start digging in
the first place.
If it works, then thats the best option.
The automake manual doesn't seem to provide enough detail for maintaining
the combination of ".py.in"-from-".py" and "_PYTHON". (And its those two
in combination which appear to be causing the problem you identified.)
One quesiton... why is that makefile dealing with .pyc files in the first place?
I dont believe they're used anywhere are they?
I'll consider raising a query on the automake email list. But I'm shortly
going out of email contact for a couple of weeks.
All the best.
--
: David Lee I.T. Service :
: Senior Systems Programmer Computer Centre :
: Durham University :
: http://www.dur.ac.uk/t.d.lee/ South Road :
: Durham DH1 3LE :
: Phone: +44 191 334 2752 U.K. :
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
