Duke4.net Forums: SVN access and compiling EDuke32 - Duke4.net Forums

Jump to content

  • 4 Pages +
  • 1
  • 2
  • 3
  • 4
  • You cannot start a new topic
  • You cannot reply to this topic

SVN access and compiling EDuke32

User is offline   Plagman 

  • Former VP of Media Operations

#31

If I recall correctly, MinGW ships with some DirectInput related symbols inside its own libraries, causing the the DirectX SDK you installed on top of MinGW to duplicate symbols. However, MinGW doesn't ship with all the symbols needed to build EDuke32, so the SDK is still needed.
I think you need to remove the libdxguid.a that came with the DirectX SDK and it'll work fine.
0

User is offline   supergoofy 

#32

@Plagman, I already uploaded a complete compile environment. He just had to check the correct topic. That's why TX organized the forum and the topics. :)
0

User is offline   Plagman 

  • Former VP of Media Operations

#33

Neither your reply nor anything in that thread contains the necessary information to address the particular problem this poster is running into. I don't see how starting from scratch with a newly setup environment is a better way to solve a problem than trying to understand the issue at hand. Besides, there's no way I'd personally run binaries that someone else repackaged and hosted on a place like mediafire, and I expect other (sane) people to be reluctant to do that as well.

This post has been edited by Plagman: 31 May 2009 - 10:50 AM

0

User is offline   supergoofy 

#34

The packs I posted are only the compiling environment, they don't contain anything else. Everyone can download the individual packs and combine them together. I don't know if it is a matter of sanity or not, but the packs are there for people that don't have the knowledge. I didn't violate any rules or insulted anyone by providing these packs. Everyone is free to choose, as long there are choices. :)
0

#35

View PostPlagman, on May 31 2009, 02:35 PM, said:

If I recall correctly, MinGW ships with some DirectInput related symbols inside its own libraries, causing the the DirectX SDK you installed on top of MinGW to duplicate symbols. However, MinGW doesn't ship with all the symbols needed to build EDuke32, so the SDK is still needed.
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

0

User is offline   Todd 

#36

View PostAlektorophobiA, on May 31 2009, 07:14 PM, said:

Thanks but deleting that file don't work, i have another error.


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.
0

User is offline   DarkyDan 

#37

I get the "failed building obj_win/game.o from source/game.c ! make [obj_win/game.o] Error 1" error.

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

0

User is offline   BlackDays 

#38

I am being completely serious here:

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.)
0

User is offline   supergoofy 

#39

View PostBlackDays, on Jun 12 2009, 11:25 PM, said:

I am being completely serious here:

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

0

User is offline   BlackDays 

#40

Thanks for the (quick) help, but I still am hitting the brick wall (I already tried running as administrator, and I also have UAC off.)

I also have driver signature enforcement disabled, so it's not that, either.
0

User is offline   supergoofy 

#41

read p.m.
0

User is offline   BlackDays 

#42

Thanks for the help, but I'm still running into errors with no sign of success.

I'll try some other things, and if I can get it working, I'll fill every one in.
0

User is offline   Plagman 

  • Former VP of Media Operations

#43

It doesn't look like a OS problem. Building works fine on Vista x64 here (except from the MSYS quirks you already seemed to work around). It seems something fails to include at some point. Can you post the full compilation log? Try redirecting it to a file, i.e. first start over with `make veryclean` then do `make &> buildlog`. Then attach buildlog here or post the contents on pastebin or something similar.
0

User is offline   BlackDays 

#44

View PostPlagman, on Jun 13 2009, 01:50 AM, said:

... Can you post the full compilation log? Try redirecting it to a file, i.e. first start over with `make veryclean` then do `make &> buildlog`. Then attach buildlog here or post the contents on pastebin or something similar.


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

0

User is offline   supergoofy 

#45

By the way, before you start compiling the source disable you firewall/antivirus/spyware.

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.
0

User is offline   TerminX 

  • el fundador

  #46

What? Don't turn off any firewalls to compile the source... lol. If you have some shitty antivirus that's actually preventing you from compiling, consider switching to something better. I like Avira AntiVir.
0

User is offline   supergoofy 

#47

Personally I have a very good ADSL router with very good hardware firewall.

But you can go offline and disable software firewall for the 2-5 min you will spend to compile the source.
0

User is offline   TerminX 

  • el fundador

  #48

Why waste time doing that?
0

User is offline   supergoofy 

#49

Because I experienced problems in the past with few firewalls, while I was compiling a source. And I gave you an example of such firewall. I'm only passing my experience.

Now that I have hardware firewall I don't care about software firewalls.
0

User is offline   TerminX 

  • el fundador

  #50

What kind of "hardware firewall" do you have? If it says Linksys or D-link or Netgear or anything like that, it's a cheap piece of mass produced crap, and half of them run iptables on Linux anyway, making them a software firewall. :)

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.
0

User is offline   supergoofy 

#51

View PostTX, on Jun 14 2009, 02:25 PM, said:

What kind of "hardware firewall" do you have? If it says Linksys or D-link or Netgear or anything like that, it's a cheap piece of mass produced crap, and half of them run iptables on Linux anyway, making them a software firewall. :)

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)
0

User is offline   BlackDays 

#52

Results were not different for disabling firewalls or antivirus (I didn't think it would make much of a difference.)

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.
0

User is offline   AdrianG 

#53

View PostBlackDays, on Jun 13 2009, 01:25 AM, said:

I am being completely serious here:

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

0

User is offline   HellFire 

#54

ok, so i tried to compile this too, but ive got an error, i followed all steps from here. After i installed the programs and downloaded the polymer source, i ran Mingw from the shortcut in my desktop, when i typed the first line command "mount c: /c" i ve got this error: "mount: /c: Device or resource busy". I obviously tried more than one time and i tried again after an system restart but i dont suceed. Any ideas ? ;)

This post has been edited by HellFire: 23 June 2009 - 01:54 PM

0

User is offline   AdrianG 

#55

View PostHellFire, on Jun 23 2009, 04:37 PM, said:

ok, so i tried to compile this too, but ive got an error, i followed all steps from here. After i installed the programs and downloaded the polymer source, i ran Mingw from the shortcut in my desktop, when i typed the first line command "mount c: /c" i ve got this error: "mount: /c: Device or resource busy". I obviously tried more than one time and i tried again after an system restart but i dont suceed. Any ideas ? ;)


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
0

User is offline   Plagman 

  • Former VP of Media Operations

#56

I have no idea why it tells you to mount the drive manually. /c should already be mounted to C: and the other drives should be mounted as well. Just ignore it and proceed to the next stop.
0

User is offline   HellFire 

#57

it worked, thx
0

User is offline   supergoofy 

#58

if you mount a drive in msys it stays mounted unless you unmount it
0

User is offline   supergoofy 

#59

MinGW_gcc-4.4.0-tdm-1-r2.rar
http://www.mediafire...php?wjv0kylmjtj

MSYS-1.0.11-rc-1.exe
http://www.mediafire...php?tihqwoowkzo
0

User is offline   BlackDays 

#60

For the record, I successfully compiled. (I did it on another computer and it worked flawlessly the first time I tried.)

And on that note: I have an ATI card and I have NO issues as of right now. None. At. All. ;)
0

Share this topic:


  • 4 Pages +
  • 1
  • 2
  • 3
  • 4
  • You cannot start a new topic
  • You cannot reply to this topic


All copyrights and trademarks not owned by Voidpoint, LLC are the sole property of their respective owners. Play Ion Fury! ;) © Voidpoint, LLC

Enter your sign in name and password


Sign in options