From: <alp...@ea...> - 2007-11-28 17:38:22
|
So I got this (uniformed) idea to try and compile povray. used 8 files as described in these intructions: http://arrozcru.no-ip.org/ffmpeg_wiki/tiki-index.php?page=MSys_MinGW msys.bat (if I read it right) appeared to be written for winnt. g++ cannot access/make its own files in gcc_con_debug(exact usage below) help me decide: should I give up now or is there some hope for win98se msys/mingw I made all its files by script:(to make sure it is accessing the right dir) F:\povwin36>make.exe -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug MAKE: Nothing to be done for `all'. now modify all c and cpp files. will it overwrite them? it can only try: F:\povwin36>make.exe -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug g++ -c -o gcc_con_debug/povray_fileinputoutput.o -Iwindows/console -Isource -Iso urce/patches -Isource/base -Isource/frontend -Ilibraries/jpeg -Ilibraries/png -I libraries/zlib -Ilibraries/tiff/libtiff -Wno-multichar -Wno-conversion -DCOMMONC TRL_VERSION=0x0400 -g source/base/fileinputoutput.cpp - Cannot openMAKE: *** [gcc_con_debug/povray_fileinputoutput.o] Error 1 back to error #1 |
From: Tim S. <sta...@ve...> - 2007-11-29 01:13:15
|
> > F:\povwin36>make.exe -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug > MAKE: Nothing to be done for `all'. > Are you sure that your are using the right make command? Most software uses mingw32-make with a makefile called "makefile.gcc" When you use make in MSys it should normmaly be procedured by configure command, was it in your case? What software are you trying to compile? Your link implied FFMPEG, but your error messages look more like wxWidgets, instead. Note, I have not yet compiled FFMPEG. Tim S |
From: <alp...@ea...> - 2007-11-29 01:36:49
|
Hi Tim! good of you to be there, >What software are you trying to compile? POVray here are steps taken with the help of Nicolas: (starting somewhere in the middle of the thread) http://news.povray.org/povray.programming/thread/%3Cweb.3f46c4398e69b4cac222 40400%40news.povray.org%3E/?mtop=10&moff=20 (thats all the setup I have done, so more likely needed) having problems with msys.bat, runs 3 command.com wins, second 2 close, first remains open with "bad command or file name" "no instructions to be found" is why I draw a blank when you say. >When you use make in MSys it should normmaly be procedured by configure >command, was it in your case? rem out the "exit" commands from msys.bat (for error msgs) MINGW32:/home - Cannot open HanSolo@HANSOLO /home $ this time 3rd window (M sh) didnt close but mouse-wait-icon persists (i think it crashed this time, ususally closes) where are the setup instructions for msys thank you, Greg |
From: Tim S. <sta...@ve...> - 2007-11-29 07:44:12
|
FYI: Build command used was mingw32-make -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug CPPFLAGS="-DDISTRIBUTION_MESSAGE_2=\"TimS\"" Please replace TimS with your name instead. I edited Windows/Console/config.h to match my MinGW setup. I had to replace my w32api with version 3.7. http://downloads.sourceforge.net/mingw/w32api-3.7.tar.gz?use_mirror=superb-east It errored out on povmsend.cpp line 895 after the above work. After removing code, it compiled, but the code really needs fixed at that location. An povray.exe was created. Tim S |
From: <alp...@ea...> - 2007-11-29 16:46:05
|
At 07:22 AM 11/29/07 +0000, you wrote: > >FYI: > >Build command used was > >mingw32-make -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug CPPFLAGS="->DDISTRIBUTION_MESSAGE_2=\"TimS\"" "bad command or file name" since there is no file "mingw32-make.exe", I am thinking there should be a "make.exe" in f:\msys\mingw\mingw32\bin and path set to same? (there is no make.exe" in that dir) currently PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;F:\MSYS\BIN;F:\MSYS\MINGW\BIN path to mingw32 dir f:\msys\mingw\mingw32\ was this even installed correctly? overwrote win32api 3.9 with 3.7 dir structure is: F:\MSYS\MINGW\INCLUDE\ And just to make sure F:\MSYS\INCLUDE\ maybe a path needs to be set to this include dir? still wont open/make its first file: F:\povwin36>make.exe -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug g++ -c -o gcc_con_debug/povray_fileinputoutput.o -Iwindows/console -Isource -Iso urce/patches -Isource/base -Isource/frontend -Ilibraries/jpeg -Ilibraries/png -I libraries/zlib -Ilibraries/tiff/libtiff -Wno-multichar -Wno-conversion -DCOMMONC TRL_VERSION=0x0400 -g source/base/fileinputoutput.cpp - Cannot openMAKE: *** [gcc_con_debug/povray_fileinputoutput.o] Error 1 (distribution was already edited in optout.h) msys dir structure is the only possible prob that I can imagine. what is yours? |
From: Tim S. <sta...@ve...> - 2007-11-29 07:42:20
|
MSys was not used during my compile test. I ran mingw32-make from standard CMD prompt Using MinGW setup below. GNU ld version 2.17.50 20060824 gcc version 3.4.5 (mingw special) GNU Make 3.81 __MINGW32_VERSION 3.13 __W32API_VERSION 3.7 Tim S |
From: <alp...@ea...> - 2007-11-29 17:10:29
|
At 07:27 AM 11/29/07 +0000, you wrote: >Using MinGW setup below. > >GNU ld version 2.17.50 20060824 >gcc version 3.4.5 (mingw special) >GNU Make 3.81 >__MINGW32_VERSION 3.13 >__W32API_VERSION 3.7 What I currently have: (not including msys files*2) gcc-g++-3.4.5-20060117-1.tar.gz gcc-core-3.4.5-20060117-1.tar.gz mingw-runtime-3.12.tar.gz w32api-3.7.tar.gz binutils-2.17.50-20070129-1.tar.gz bash-3.1-MSYS-1.0.11-snapshot.tar.bz2 what file to needs to be downloaded for mingw32-make.exe is it on this page? http://sourceforge.net/project/showfiles.php?group_id=2435 |
From: Tim S. <sta...@ve...> - 2007-11-29 16:52:41
|
>>FYI: >> >>Build command used was >> >>mingw32-make -f windows\makefiles\makefile.gcc USE_GUI=0 BUILD=debug > CPPFLAGS="->DDISTRIBUTION_MESSAGE_2=\"TimS\"" > > "bad command or file name" > since there is no file "mingw32-make.exe", > > I am thinking there should be a "make.exe" in f:\msys\mingw\mingw32\bin > and path set to same? (there is no make.exe" in that dir) > Yes, mingw32-make.exe is part of MinGW and should be in the bin folder. It is normaly in C:\MinGW\bin folder; I think you need to install MinGW correctly without the MSys installation. Tim S |
From: Tim S. <sta...@ve...> - 2007-11-29 22:47:56
|
> > > Really? I have never heard that. What difference can the location of the > source possibly make? The issue never happened to me, but when a source includes a system header sometimes it can not find the header. It related to the fact that MinGW looks in \MinGW\Include by default. Tim S |
From: Greg C. <gch...@sb...> - 2007-11-30 16:41:39
|
On 2007-11-29 22:47Z, Tim Stahlhut wrote: >> >> Really? I have never heard that. What difference can the location of the >> source possibly make? > > The issue never happened to me, but when a source includes a system > header sometimes it can not find the header. > > It related to the fact that MinGW looks in \MinGW\Include by default. Does that still occur since Aaron's patch http://gcc.gnu.org/ml/gcc-patches/2004-06/msg00703.html was accepted? |
From: Keith M. <kei...@us...> - 2007-11-30 16:58:20
|
On Thursday 29 November 2007 16:51, Tim Stahlhut wrote: > >>Build command used was > >> > >>mingw32-make -f windows\makefiles\makefile.gcc USE_GUI=0 > >> BUILD=debug > > > > CPPFLAGS="->DDISTRIBUTION_MESSAGE_2=\"TimS\"" > > > > "bad command or file name" > > since there is no file "mingw32-make.exe", > > > > I am thinking there should be a "make.exe" in > > f:\msys\mingw\mingw32\bin and path set to same? If you plan to use MSYS, then no, there should *not* be; it should be called mingw32-make.exe, if you've installed it according to our standard, although it is acceptable to shorten it to gmake.exe if you prefer shorter command names. When you install MSYS, *it* provides its own make.exe, in its own /bin directory. MinGW must *not* be installed into the same directory as MSYS, (unless you are trialling the technology preview of MSYS-1.0.11); however, it is acceptable to install MinGW into a /mingw subdirectory of the MSYS tree, which is what the OP appeared to have, so that would not have been his problem. > > (there is no make.exe" in that dir) Nor should there be; MinGW's bin directory should come *before* the MSYS /bin directory, in the $PATH set for the MSYS shell, but you want to be able to run the MSYS make.exe in that environment; thus you *must* use a different name for MinGW's make. > Yes, mingw32-make.exe is part of MinGW... but it is packaged separately, and is an optional install; perhaps the OP neglected to install it. > and should be in the bin folder. MinGW's bin directory, yes; *not* in the MSYS /bin directory. > It is normaly in C:\MinGW\bin folder; That is certainly the default, and we *strongly* recommend keeping it that way, unless you *really* know what you are doing; (and those who think it might be a good idea to tuck it into `Program Files' do *not* have the necessary expertise). > I think you need to install MinGW correctly without the MSys > installation. The OP's installation looked fine to me, except that it was missing mingw32-make. Regards, Keith. |
From: <alp...@ea...> - 2007-12-01 07:42:34
|
At 04:39 PM 11/30/07 +0000, you wrote: >The OP's installation looked fine to me, except that it was missing >mingw32-make. > >Regards, >Keith. > This was my final conclusion, thank you for the support. If one reads further posts you'd know I have an EXE now. povray.exe = 6,512,775 Any chance to yak with intelligent life forms is awesome. Hi Keith, (or anyone else out there) Got stuck here again F:/povwin36/windows/pvengine.cpp:2218: undefined reference to `PlaySoundA@12' gcc_gui_debug/pvengine_pvtext.o: In function `Z14create_toolbarP6HWND__': F:/povwin36/windows/pvtext.cpp:1581: undefined reference to `_imp__ImageList_Create@20' PlaySoundA is found in cmedit32.dll so it seems to me the compiler has not been informed of the externals. where would this be corrected? makefile? or another place? (and how exactly) BUT this one boggles: the reference is ImageList_Create (cmedit.dll) NOT _imp__ImageList_Create _imp__ImageList_Create <not found Whats up with that! greatly appreciated, ?OP? |
From: Earnie B. <ea...@us...> - 2007-12-02 05:59:37
|
Quoting alp...@ea...: > > Hi Keith, (or anyone else out there) > > Got stuck here again > > > F:/povwin36/windows/pvengine.cpp:2218: undefined reference to `PlaySoundA@12' > gcc_gui_debug/pvengine_pvtext.o: In function `Z14create_toolbarP6HWND__': > F:/povwin36/windows/pvtext.cpp:1581: undefined reference to > `_imp__ImageList_Create@20' > > You need to tell the linker what library to use. I used ``grep -li playsounda /mingw/lib/*'' to find it in libwinmm.a. From there I know to add -lwinmm to the link command. Earnie |
From: Tim S. <sta...@ve...> - 2007-11-29 17:00:15
|
FYI: When compiling using MinGW GCC it is reccommended to have the Compiler and the source code on the same drive letter. There have been complaints form some people that this fixes compiler directory search issues for some people. Tim S |
From: John B. <joh...@ho...> - 2007-11-29 18:27:59
|
> > FYI: > > When compiling using MinGW GCC it is reccommended to have the Compiler > and the source code on the same drive letter. > > There have been complaints form some people that this fixes compiler > directory search issues for some people. > > Tim S Really? I have never heard that. What difference can the location of the source possibly make? _________________________________________________________________ Your smile counts. The more smiles you share, the more we donate.=A0 Join i= n. www.windowslive.com/smile?ocid=3DTXT_TAGLM_Wave2_oprsmilewlhmtagline= |
From: <alp...@ea...> - 2007-11-29 18:59:58
|
tim did you use Nicolas' makefile.ggc with changed slashes? compiler whining about zlib definitions is zlib supposed to be a precompiled header? also unistd.h is not found in any of this, but I had it from compiling openuniverse (now with about 100 new features, from gravity to autopilot) |
From: Tim S. <sta...@ve...> - 2007-11-29 22:29:56
|
alp...@ea... wrote: > sourceforge Try this link for mingw32-make-3.81-2.tar.gz http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=23918 Tim S |
From: Keith M. <kei...@us...> - 2007-11-30 16:59:47
|
On Thursday 29 November 2007 18:27, John Brown wrote: > > When compiling using MinGW GCC it is reccommended to have the > > Compiler and the source code on the same drive letter. > > > > There have been complaints form some people that this fixes > > compiler directory search issues for some people. > > > > Tim S > > Really? I have never heard that. What difference can the location of > the source possibly make? This is news to me too. Strange that I've never had the slightest problem in this respect. Regards, Keith. |
From: Earnie B. <ea...@us...> - 2007-12-02 06:11:48
|
Quoting Keith Marshall <kei...@us...>: > On Thursday 29 November 2007 18:27, John Brown wrote: >> > When compiling using MinGW GCC it is reccommended to have the >> > Compiler and the source code on the same drive letter. >> > >> > There have been complaints form some people that this fixes >> > compiler directory search issues for some people. >> > >> > Tim S >> >> Really? I have never heard that. What difference can the location of >> the source possibly make? > > This is news to me too. Strange that I've never had the slightest > problem in this respect. > Once upon a time, in a land not too far away, it used to be so. Earnie |
From: Tim S. <sta...@ve...> - 2007-12-01 18:49:07
|
Greg Chicares wrote: > > Does that still occur since Aaron's patch > http://gcc.gnu.org/ml/gcc-patches/2004-06/msg00703.html > was accepted? > I have never had enough info to determine the setup of the person having the problem. But, the number of people having it has deceased a lot in recent months. I am a person who watches the Code::Blocks forum, the problem was common a year ago; but know it seems rare. Tim S |