project-navigation
Personal tools

Author Topic: Compilation Error: junk at end of line  (Read 25301 times)

odie

  • Guest
Re: Compilation Error: junk at end of line
« Reply #15 on: July 28, 2009, 10:42:07 am »
redownload the c::b package from mattn.ninex.info

Mattn,

Not too sure if i missed something along the line.

I used the new version and got these errors.....
Code: [Select]
||=== ufo, windows_debug ===|
C:\SVN Update\src\client\renderer\r_error.h|48|warning: 'R_CheckErrorDebug' defined but not used|
||=== uforadiant, windows_debug ===|
||warning: command line option "-Wno-non-virtual-dtor" is valid for C++/ObjC++ but not for C|
||warning: command line option "-Wno-non-virtual-dtor" is valid for C++/ObjC++ but not for C|
C:\SVN Update\src\tools\radiant\libs\gtkutil\filechooser.cpp|149|warning: 'shortcutFoldersInBaseDir' defined but not used|
C:\SVN Update\src\tools\radiant\radiant\exec.cpp||In function 'void exec_spawn_process(ExecCmd*, void (*)(void*))':|
C:\SVN Update\src\tools\radiant\radiant\exec.cpp|196|warning: statement has no effect|
C:\SVN Update\src\tools\radiant\radiant\exec.cpp||In function 'void exec_run(Exec*)':|
C:\SVN Update\src\tools\radiant\radiant\exec.cpp|396|warning: statement has no effect|
..\..\src\tools\radiant\include\igl.h|989|warning: "GL_LOGIC_OP" redefined|
c:\development\codeblocks\mingw\bin\..\lib\gcc\mingw32\4.4.0\..\..\..\..\include\GL\gl.h|394|warning: this is the location of the previous definition|
..\..\src\tools\radiant\include\igl.h|990|warning: "GL_TEXTURE_COMPONENTS" redefined|
c:\development\codeblocks\mingw\bin\..\lib\gcc\mingw32\4.4.0\..\..\..\..\include\GL\gl.h|626|warning: this is the location of the previous definition|
C:\SVN Update\src\tools\radiant\radiant\server.cpp|194|warning: 'dllimport' attribute ignored|
(null):.\uforadiant-de.po|197|keyword "msgctxt" unknown|
(null): .\uforadiant-de.po|197|parse error|
(null):.\uforadiant-de.po|203|keyword "msgctxt" unknown|
(null): .\uforadiant-de.po|203|parse error|
(null):.\uforadiant-de.po|209|keyword "msgctxt" unknown|
(null): .\uforadiant-de.po|209|parse error|
(null):.\uforadiant-de.po|221|keyword "msgctxt" unknown|
(null): .\uforadiant-de.po|221|parse error|
(null):.\uforadiant-de.po|227|keyword "msgctxt" unknown|
(null): .\uforadiant-de.po|227|parse error|
(null):.\uforadiant-de.po|233|keyword "msgctxt" unknown|
(null): .\uforadiant-de.po|233|parse error|
(null):.\uforadiant-de.po|1208|keyword "msgctxt" unknown|
(null): .\uforadiant-de.po|1208|parse error|
(null):.\uforadiant-de.po|2186|keyword "msgctxt" unknown|
(null): .\uforadiant-de.po|2186|parse error|
(null):.\uforadiant-de.po|2193|keyword "msgctxt" unknown|
(null): .\uforadiant-de.po|2193|parse error|
(null):.\uforadiant-de.po|2464|keyword "msgctxt" unknown|
(null): .\uforadiant-de.po|2464|parse error|
(null):.\uforadiant-en.po|187|keyword "msgctxt" unknown|
(null): .\uforadiant-en.po|187|parse error|
(null):.\uforadiant-en.po|193|keyword "msgctxt" unknown|
(null): .\uforadiant-en.po|193|parse error|
(null):.\uforadiant-en.po|199|keyword "msgctxt" unknown|
(null): .\uforadiant-en.po|199|parse error|
(null):.\uforadiant-en.po|210|keyword "msgctxt" unknown|
(null): .\uforadiant-en.po|210|parse error|
(null):.\uforadiant-en.po|216|keyword "msgctxt" unknown|
(null): .\uforadiant-en.po|216|parse error|
(null):.\uforadiant-en.po|222|keyword "msgctxt" unknown|
(null): .\uforadiant-en.po|222|parse error|
(null):.\uforadiant-en.po|1155|keyword "msgctxt" unknown|
(null): .\uforadiant-en.po|1155|parse error|
(null):.\uforadiant-en.po|2110|keyword "msgctxt" unknown|
(null): .\uforadiant-en.po|2110|parse error|
(null):.\uforadiant-en.po|2117|keyword "msgctxt" unknown|
(null): .\uforadiant-en.po|2117|parse error|
(null):.\uforadiant-en.po|2366|keyword "msgctxt" unknown|
(null): .\uforadiant-en.po|2366|parse error|
(null):.\uforadiant-ru.po|191|keyword "msgctxt" unknown|
(null): .\uforadiant-ru.po|191|parse error|
(null):.\uforadiant-ru.po|197|keyword "msgctxt" unknown|
(null): .\uforadiant-ru.po|197|parse error|
(null):.\uforadiant-ru.po|203|keyword "msgctxt" unknown|
(null): .\uforadiant-ru.po|203|parse error|
(null):.\uforadiant-ru.po|214|keyword "msgctxt" unknown|
(null): .\uforadiant-ru.po|214|parse error|
(null):.\uforadiant-ru.po|220|keyword "msgctxt" unknown|
(null): .\uforadiant-ru.po|220|parse error|
||More errors follow but not being shown.|
||Edit the max errors limit in compiler options...|
||=== Build finished: 50 errors, 11 warnings ===|

its something to do with the po translations..... i could compile using my old cb version, but not this new one. Hmmmm.

My current windows uses version CB 5456.
It could compile just fine even this morning.
Advise pls?

Offline bfett14

  • Rookie
  • ***
  • Posts: 10
    • View Profile
Re: Compilation Error: junk at end of line
« Reply #16 on: July 29, 2009, 05:20:34 am »
Great success. Hello world compiles and the game too!  ;D
Thanks a lot. For my education, what's changed in the C:B ?
I noticed assembler is a bit newer.
Cheers.

Offline Mattn

  • Administrator
  • PHALANX Commander
  • *****
  • Posts: 4831
  • https://github.com/mgerhardy/vengi
    • View Profile
    • Vengi Voxel Tools
Re: Compilation Error: junk at end of line
« Reply #17 on: July 29, 2009, 03:26:16 pm »
yes - assembler didn't fit to compiler (binutils was not up-to-date)

odie

  • Guest
Re: Compilation Error: junk at end of line
« Reply #18 on: July 29, 2009, 06:04:16 pm »
yes - assembler didn't fit to compiler (binutils was not up-to-date)

Mattn, a bit confused here. Were u answering my queries?? As in the reason why that CB fails was because the assembler issues?

If so how do i fix it pls?

If thats not answering my queries earlier, could u advise me on the nx step pls? Thanks.
Its on win32 xp pro sp3 platform btw. :D

Offline Duke

  • Administrator
  • PHALANX veteran
  • *****
  • Posts: 1037
    • View Profile
Re: Compilation Error: junk at end of line
« Reply #19 on: July 31, 2009, 10:10:48 pm »
Odie,
Mattn's answer was directed at bfett14.

The errors you get from compiling the po files are NOT solved by the latest C:B package (I get them too).
I'm not even sure that they are related to C:B.

Offline Muton

  • Sergeant
  • *****
  • Posts: 496
    • View Profile
Re: Compilation Error: junk at end of line
« Reply #20 on: August 01, 2009, 08:28:52 am »
C::B run ufoai\contrib\scripts\compile_po.bat

> i could compile using my old cb version, but not this new one
Than mabe this is the solution
http://sourceforge.net/projects/mingw/files/MinGW%20gettext/gettext-0.17-1/gettext-0.17-1-mingw32-bin.tar.lzma/download

odie

  • Guest
Re: Compilation Error: junk at end of line
« Reply #21 on: August 01, 2009, 06:31:10 pm »
Odie,
Mattn's answer was directed at bfett14.

Ah, thanks. No wonder its a bit wierd wierd de.



The errors you get from compiling the po files are NOT solved by the latest C:B package (I get them too).
I'm not even sure that they are related to C:B.


Not too sure abt this. I suspect its the gettext version part. Then again........

see this:

C::B run ufoai\contrib\scripts\compile_po.bat

> i could compile using my old cb version, but not this new one
Than mabe this is the solution
http://sourceforge.net/projects/mingw/files/MinGW%20gettext/gettext-0.17-1/gettext-0.17-1-mingw32-bin.tar.lzma/download

I checked the compile_po.bat file, which is integrated into the CB workspace script -> not working.

As for the 0.17 gettext version, maybe i try tat on Monday again. I tried once already, not working either last wed and thurs. I tried replacing the current gettext version with tat. Not work.

I tried replacing only the newer (and smaller) files, not work either.

I tried to path both directories (WORSE CHOICE), not work.

Hmmmm, i reverted back to the old version since. Lol. No one's complaining....yet.


odie

  • Guest
Re: Compilation Error: junk at end of line
« Reply #23 on: August 02, 2009, 08:03:50 pm »
Than use this
http://sourceforge.net/projects/mingw/files/MinGW%20gettext/gettext-0.17-1/gettext-0.17-1-mingw32-dev.tar.lzma/download

Eh, I am running windows....

The file says cannot open. Is it a 7zip archive or winrar/winzip compatible archive?
This file seemed to give me prob. Do u have the checksum for it? I check to make sure first.

Offline Muton

  • Sergeant
  • *****
  • Posts: 496
    • View Profile
Re: Compilation Error: junk at end of line
« Reply #24 on: August 03, 2009, 06:04:25 pm »
7zip can open it
its just a tar archive

md5
4d5ba071c742dcdcc7038614d1b0a0f7 *gettext-0.17-1-mingw32-dev.tar.tar

Offline Thyranim

  • Rookie
  • ***
  • Posts: 77
    • View Profile
Re: Compilation Error: junk at end of line
« Reply #25 on: August 03, 2009, 06:44:04 pm »
7zip can open it
definitely, done this here ;)

its just a tar archive
mh, nah... it's a lzma-archived tar-archive, because of this winrar is not possible to open it
have to use 7zip