SVN access and compiling EDuke32
#31 Posted 31 May 2009 - 10:35 AM
I think you need to remove the libdxguid.a that came with the DirectX SDK and it'll work fine.
#32 Posted 31 May 2009 - 10:39 AM
#33 Posted 31 May 2009 - 10:50 AM
This post has been edited by Plagman: 31 May 2009 - 10:50 AM
#34 Posted 31 May 2009 - 11:02 AM
#35 Posted 31 May 2009 - 03:14 PM
Plagman, on May 31 2009, 02:35 PM, said:
I think you need to remove the libdxguid.a that came with the DirectX SDK and it'll work fine.
Thanks but deleting that file don't work, i have another error.
This post has been edited by AlektorophobiA: 31 May 2009 - 03:16 PM
#36 Posted 31 May 2009 - 05:16 PM
AlektorophobiA, on May 31 2009, 07:14 PM, said:
What worked for me a couple weeks ago...
in one of the source files--I think it's in the build directory, but I can't remember which .c file, there is a comment that says "if you get "xxx multiply defined" errors, comment out the following line"
and commenting out that line gets you past that particular error.
#37 Posted 02 June 2009 - 09:45 PM
Scratch that I hadn't ran the preinstall after the MSYS update!.. seems to be going smoothly now.
This post has been edited by DarkyDan: 02 June 2009 - 09:57 PM
#38 Posted 12 June 2009 - 10:25 PM
I have a Vista x64 machine. I'm guessing that this is the reason I am having zero luck with compiling the Eduke source code? I've followed all of the directions down to the last drop, including the ones in this thread that have worked for other people. My compile log goes on for a mile and a half of errors, mostly regarding the absence of certain symbols (much like the following):
build/include/build.h:232: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'parallaxyoffs'
build/include/build.h:233: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'visibility'
build/include/build.h:235: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'windowx1'
and then of course since it isn't processing this info correctly, anything referenced in these lines (there are literally hundreds of them) gives errors like the following:
source/game.c:13712: error: 'sectortype' has no member named 'floorz'
source/game.c:13712: error: 'sectortype' has no member named 'ceilingz'
source/game.c:13712: error: 'sectortype' has no member named 'floorz'
source/game.c:13714: error: 'spritetype' has no member named 'z'
and so on until finally giving me the Error 1 message and telling me it couldn't make game.o
Again I paraphrased the logs for the sake of avoiding gigantic compile logs.
Does MinGW just hate Vista x64? I know I had trouble along the way with MSYS (no longer a problem with that.)
#39 Posted 12 June 2009 - 10:44 PM
BlackDays, on Jun 12 2009, 11:25 PM, said:
I have a Vista x64 machine. I'm guessing that this is the reason I am having zero luck with compiling the Eduke source code? I've followed all of the directions down to the last drop, including the ones in this thread that have worked for other people. My compile log goes on for a mile and a half of errors, mostly regarding the absence of certain symbols (much like the following):
build/include/build.h:232: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'parallaxyoffs'
build/include/build.h:233: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'visibility'
build/include/build.h:235: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'windowx1'
and then of course since it isn't processing this info correctly, anything referenced in these lines (there are literally hundreds of them) gives errors like the following:
source/game.c:13712: error: 'sectortype' has no member named 'floorz'
source/game.c:13712: error: 'sectortype' has no member named 'ceilingz'
source/game.c:13712: error: 'sectortype' has no member named 'floorz'
source/game.c:13714: error: 'spritetype' has no member named 'z'
and so on until finally giving me the Error 1 message and telling me it couldn't make game.o
Again I paraphrased the logs for the sake of avoiding gigantic compile logs.
Does MinGW just hate Vista x64? I know I had trouble along the way with MSYS (no longer a problem with that.)
In Windows XP x64 works ok though. The compilation pack should work on Vista too. Maybe you should run msys as admin. Vista is a stupid and hungry OS that needs a lot of configuration/customization to make it work correctly for the above average user. In other words, you have first to remove the crap that has, then it becomes a good OS.
This post has been edited by supergoofy: 12 June 2009 - 10:48 PM
#40 Posted 12 June 2009 - 10:52 PM
I also have driver signature enforcement disabled, so it's not that, either.
#42 Posted 13 June 2009 - 12:00 AM
I'll try some other things, and if I can get it working, I'll fill every one in.
#43 Posted 13 June 2009 - 12:50 AM
#44 Posted 13 June 2009 - 01:45 AM
Plagman, on Jun 13 2009, 01:50 AM, said:
Done.
http://pastebin.com/m7bea6994
Thanks again guys, I promise the content that comes from this will be awesome.
This post has been edited by BlackDays: 13 June 2009 - 01:51 AM
#45 Posted 14 June 2009 - 12:47 PM
For example if you have Agnitum Outpost you will get errors and the compilation of source will be aborted.
Shut off completely antivirus, firewall, spyware and the start the compilation of the source.
#46 Posted 14 June 2009 - 01:09 PM
#47 Posted 14 June 2009 - 01:15 PM
But you can go offline and disable software firewall for the 2-5 min you will spend to compile the source.
#49 Posted 14 June 2009 - 01:21 PM
Now that I have hardware firewall I don't care about software firewalls.
#50 Posted 14 June 2009 - 01:25 PM
However, it just so happens that iptables on Linux is all you need, so some of those cheap routers are pretty awesome if you can throw a third party version of the firmware on them and use them as a really low spec Linux server.
#51 Posted 14 June 2009 - 01:32 PM
TX, on Jun 14 2009, 02:25 PM, said:
However, it just so happens that iptables on Linux is all you need, so some of those cheap routers are pretty awesome if you can throw a third party version of the firmware on them and use them as a really low spec Linux server.
zynos (zyxel router)
#52 Posted 14 June 2009 - 08:27 PM
Something I noted before in a PM is that it doesn't work with any revision number of the source code, so it's obviously user error to some extent. I am officially baffled.
#53 Posted 21 June 2009 - 11:25 PM
BlackDays, on Jun 13 2009, 01:25 AM, said:
I have a Vista x64 machine. I'm guessing that this is the reason I am having zero luck with compiling the Eduke source code? I've followed all of the directions down to the last drop, including the ones in this thread that have worked for other people. My compile log goes on for a mile and a half of errors, mostly regarding the absence of certain symbols (much like the following):
build/include/build.h:232: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'parallaxyoffs'
build/include/build.h:233: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'visibility'
build/include/build.h:235: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'windowx1'
and then of course since it isn't processing this info correctly, anything referenced in these lines (there are literally hundreds of them) gives errors like the following:
source/game.c:13712: error: 'sectortype' has no member named 'floorz'
source/game.c:13712: error: 'sectortype' has no member named 'ceilingz'
source/game.c:13712: error: 'sectortype' has no member named 'floorz'
source/game.c:13714: error: 'spritetype' has no member named 'z'
and so on until finally giving me the Error 1 message and telling me it couldn't make game.o
Again I paraphrased the logs for the sake of avoiding gigantic compile logs.
Does MinGW just hate Vista x64? I know I had trouble along the way with MSYS (no longer a problem with that.)
I'd be willing to bet you're missing packages, and therefore header files. I was getting parse errors as well before installing binutils, mingw-runtime, and w32api...after installing these make goes well but its not linking the exe.
c:/mingw/bin/../lib/gcc/mingw32/4.3.3/../../../. ./mingw32/bin/ld.exe: cannot find -lsupc++
collect2: ld returned 1 exit status
Failed linking executable eduke32.exe!
make: *** [eduke32.exe] Error 1
Looks like I'm still missing something but hopefully after this I'll be golden
[edit] Oh, maybe installing g++ would help, lol. I must be tired. *facepalm*
Linked executable eduke32.exe
Linked executable mapster32.exe
Build successful
This post has been edited by AdrianG: 21 June 2009 - 11:30 PM
#54 Posted 23 June 2009 - 01:37 PM
This post has been edited by HellFire: 23 June 2009 - 01:54 PM
#55 Posted 24 June 2009 - 08:20 PM
HellFire, on Jun 23 2009, 04:37 PM, said:
Is your hard disk assigned the drive letter "c" in windows, or is it "d" or something else? Also, have you tried mounting to another drive letter? For instance:
"mount c: /x" (assuming your disk drive is using the letter "c" in windows)
and then "cd /x/src_dir/", etc
#56 Posted 25 June 2009 - 03:28 AM
#58 Posted 26 June 2009 - 12:35 PM
#59 Posted 12 July 2009 - 10:51 PM
http://www.mediafire...php?wjv0kylmjtj
MSYS-1.0.11-rc-1.exe
http://www.mediafire...php?tihqwoowkzo
#60 Posted 13 July 2009 - 04:13 PM
And on that note: I have an ATI card and I have NO issues as of right now. None. At. All.