Yes, it looks like I was missing the necessary headers. Once I
replaced them, it has been smooth sailing.
Thank you for your assitance, Martin.
--
http://mail.python.org/mailman/listinfo/python-list
smurphus wrote:
> I hope that information is of some use. Not sure where to go from
> here.
Please try
gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp
-mno-fused-madd -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I.
-I./Include -DPy_BUILD_CORE -c ./Modules/posixmodule.c -o
Modules/posixm
configure also reports
checking for statvfs... yes
--
http://mail.python.org/mailman/listinfo/python-list
I just re-ran the configure script.
It reports:
checking for lchown... yes
checking for fstatvfs... yes
??
--
http://mail.python.org/mailman/listinfo/python-list
Thanks for the reply, Martin.
I know a bit of C. I thought maybe I was missing something simple,
since I don't have an exotic system configuration.
Re: lchown
the file posixmodule.c in Python does include and I have
that header where it should be, i.e. /usr/include/sys/types.h so I
don't know w
smurphus wrote:
> Any suggestions on how I can remedy this?
It would be good if you could try to understand and to
analyse these error messages; your message does not
indicate whether you have knowledge of the C language
and could analyse them or not.
For example, it is very puzzling that there i
Hi All-
I'm trying to build Python 2.4.2 on OSX 10.4.3 (gcc ver. 3.3 apple
build 1495) and have the following error when running 'make':
gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp
-mno-fused-madd -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I.
-I./Include -DPy_BUILD_CORE -c ./Modul
