Where is .../png.d

#1 I'm a Win user, but just in case you haven't found the docs yet, here is a link for compiling under linux:

Compiling under linux

and here is a link to the online docs.

If you've already tried this you might re-ping this forum in about a day if you don't get help from someone by then.

Good luck!
-Ed

#2 Giao, if you are getting a specific error message, please post it. Generally the .d files are autogenerated by the compiler. They contain a list of the dependent header files for a give source file.

#3 please help:

when I type

"Make -f mk/configure.mk OS=LINUX COMPILER=GCC2 BUILD=DEBUG"
It said VALID
And then I type "make"
The very first file "...Compile lpng/png.c "
" out.GCC2.DEBUG/lpng/png.d: No such file or directory
make[1]: *** [out.GCC2.DEBUG/lpng/png.obj] Error 1
make: 888 [default] Error 2

----------------
Hoe can I pass this point. I am compiling for the first time, with LINUX 2.4.4.
Thank you.

#4 What version of make are you using? (make --version)
What version of gcc? (gcc --version)

Try running this command from the top level torque folder:

find lib -name "png.d" -print

Does it find any files?

#5 I am researching this un common way of compiling. I know from my file, it is the LIBPNG and ZLIB.
there is no png.d file, because the soucre code .../lib/lpn/png.c suppose to open ( MKdir ) a directory call "out" but It never did create this directory.

From the DIR.OBJ variable in conf.mk. It said that is where a directory name "out" should be created.
I am experiment with installing "libpng" and "Zlib" of GNU , and will not bother with this local and unconventional way, TORQUE is compiling libpng.

Unless you know a better way, and I think you do, to get this TORQUE to compile. I amusing the HEAD version. and I am using gcc3.2 the newest gcc compiller.
I may have to go back to gcc2.x

#6 I know that gcc 3.2 works with torque, I've used it many times.

You didn't mention what make version you are using. It maybe a problem with your make.

You can try removing the -MD flag from conf.UNIX.mk. Then the compiler won't try to generate the .d files, which are really mini-makefiles that contain dependency information for the source. This isn't the ideal solution since you won't be able to rebuild properly after making changes, but it might be enough to get you going.

#7 Hi, Jhon Quintley.

I switch back to gcc2.9.5 and totally refresh, and reload my linux to 2.4.4-4GB from SuSE linux and original loads.
This has solve my problems. I will try to use GCC3.2 next.
But this time I will use the older MAKE facilities.
Thank you so much.

It works :)

#8 Not sure I really did anything to help, but you're welcome anyway :)