[Bf-committers] python freeze thing

John K. Walton bf-committers@blender.org
Sat, 1 Feb 2003 09:04:41 -0500 (EST)

latest code compiled/ran under traditional makefiles, but failed
with auto* gcc on irix

gmake[4]: Entering directory `/usr/demos/gcc/intern/python/freeze' cd
../../.. && /bin/sh ./config.status intern/python/freeze/Makefile On 1 Feb
2003, Michel Selten wrote: config.status: creating
intern/python/freeze/Makefile gmake[4]: Leaving directory
`/usr/demos/gcc/intern/python/freeze'> Hi, gmake[4]: Entering directory
`/usr/demos/gcc/intern/python/freeze'> gmake[4]: *** No rule to make
target `config.c', needed by `../frozen/src.list'.  Stop.> As you may have
notices I'm working a bit on the Python freeze thing in gmake[4]: Leaving
directory `/usr/demos/gcc/intern/python/freeze'> Blender :) gmake[3]: ***
[all-recursive] Error 1> gmake[3]: Leaving directory
`/usr/demos/gcc/intern/python'> I have a question. There is a difference
in makemakefile.py and gmake[2]: *** [all-recursive] Error 1>
makemakefile_ac.py. gmake[2]: Leaving directory `/usr/demos/gcc/intern'>
In makemakefile.py the output is also being generated in gmake[1]: ***
[all-recursive] Error 1> source/blender/bpython/frozen. gmake[1]: Leaving
directory `/usr/demos/gcc'> In makemakefile_ac.py it is not. I see in the
history of makemakefile.py gmake: *** [all] Error 2> that this copy action
has been added, but it has not been added to the
sgi68 105% 

> _ac version. (happend in november last year)
> Also, what should the intended result be? I mean, I can build the
> source/blender/bpython library without the source/blender/bpython/frozen
> files.
> with regards,
> 	Michel
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers