Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: therion on December 05, 2005, 07:19:39 pm

Title: wxScintilla build error on HEAD
Post by: therion on December 05, 2005, 07:19:39 pm
Hello :-)

Im not being able to build scintilla unsing newer codeblocks releases.
I don't know exactly when this started to happen but i compile anything on 1421, and shows this error msg when i try to compile C::B using C::B HEAD:

Code
Linking dynamic library: devel\wxscintilla.dll
The following character string is too long:
 -shared  -Wl,--out-implib=devel\libwxscintilla.a -Wl,--dll -Lsdk\tinyxml -Lc:\wx\lib\gcc_dll\msw -Lc:\wx\lib\gcc_dllNonUnicode -LC:\MinGW\lib -LC:\wx\lib\gcc_dll  .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexKix.o .objs\2.6\sdk\wxscintilla\src\ScintillaWX.osrc\scintilla\src\Document.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\DocumentAccessor.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\Editor.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\ExternalLexer.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\Indicator.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\KeyMap.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\KeyWords.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexAPDL.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexAU3.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexAVE.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexAda.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexAsm.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexAsn1.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexBaan.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexBash.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexBasic.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexBullant.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexCLW.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexCPP.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexCSS.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexCaml.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexConf.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexCrontab.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexCsound.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexEScript.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexEiffel.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexErlang.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexFlagship.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexForth.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexFortran.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexGui4Cli.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexHTML.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexHaskell.o .objs\2.6\sdk\wxscintilla\src\PlatWX.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexLisp.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexLout.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexLua.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexMMIXAL.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexMPT.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexMSSQL.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexMatlab.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexMetapost.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexNsis.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexOthers.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexPB.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexPOV.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexPS.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexPascal.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexPerl.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexPython.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexRebol.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexRuby.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexSQL.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexScriptol.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexSmalltalk.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexSpecman.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexTADS3.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexTeX.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexVB.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexVHDL.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexVerilog.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LexYAML.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\LineMarker.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\PropSet.o .objs\2.6\sdk\wxscintilla\src\scintilla\src\RESearch.o .objs\2.6\sdk\wxscintilla\src\scintilla\sr
Process terminated with status 1 (1 minutes, 53 seconds)
0 errors, 8 warnings

Thx
Title: Re: wxScintilla build error on HEAD
Post by: Michael on December 05, 2005, 07:29:45 pm
Hello,

Could be that your string:

-shared -W1...

is too long? Could you try to split it?

Best wishes,
Michael
Title: Re: wxScintilla build error on HEAD
Post by: therion on December 05, 2005, 07:56:54 pm
Hi

This is happening when i try to build Codeblocks-newbuild.cbp...

Regards
Title: Re: wxScintilla build error on HEAD
Post by: kisoft on December 07, 2005, 10:39:36 am
Quote from: therion on December 05, 2005, 07:19:39 pm
Hello :-)

Im not being able to build scintilla unsing newer codeblocks releases.
I don't know exactly when this started to happen but i compile anything on 1421, and shows this error msg when i try to compile C::B using C::B HEAD:

Code
Linking dynamic library: devel\wxscintilla.dll
The following character string is too long:
... deleted by kisoft ...
Process terminated with status 1 (1 minutes, 53 seconds)
0 errors, 8 warnings

Thx

Temporary solve a problem (for Win only ? I test this method on my Win2k):

Menu: Project/Properties
Select page: Targets
Choose target: scintilla
Change parameter: Objects output dir:
  from: .obj\2.6
  to: .o

After change and rebuild, all right!

This solve a problem - temporary!

Good luck!
Title: Re: wxScintilla build error on HEAD
Post by: thomas on December 07, 2005, 11:59:13 am
The linker is given too long a commandline, which may be due to
1. too many link libraries / objects
2. too long library / object names (paths)
3. too many unncessary library paths
4. too long library paths

#1 we can't change, you can't just leave out some libraries, #2 can be tweaked like you did.
However, #3 and #4 might be worth being looked into.
Do you have any long linker paths set up in compiler options which are not strictly necessary? It is because I have none, and for me it works, so that might just be it. Apart from that, I'll look into the project to see whether there is something that can be left out.
Title: Re: wxScintilla build error on HEAD
Post by: thomas on December 07, 2005, 12:18:56 pm
Try if the attached project file works for you.

I've removed -lwxmsw and -Lsdk/tinyxml for that target since they are not needed (the former is already in the project's options, and the latter in unnecessary). So this produces identical output.

If that works for you, then I'd commit it like this, that will be better than changing path names (which might cause a problem with someone else if, for whatever reason, someone relies on an output path).

[attachment deleted by admin]
Title: Re: wxScintilla build error on HEAD
Post by: therion on December 07, 2005, 12:21:54 pm
hummm yup...
but i can still compile using last week releases... get 1421 on my site and try to build head inside it... works perfectly... it was some modification during the weekend that broke it. i don´t know exactly when but it was between 1421 and 1447

regards,

Title: Re: wxScintilla build error on HEAD
Post by: therion on December 07, 2005, 12:31:19 pm
sorry, i mean... there is nothing wrong with CodeBlocks-NewBuild.cbp, my workaround is to keep 1421 as my "main" IDE and head releases are building perfect :-)
Title: Re: wxScintilla build error on HEAD
Post by: kisoft on December 07, 2005, 12:53:17 pm
Quote from: thomas on December 07, 2005, 11:59:13 am
The linker is given too long a commandline, which may be due to
1. too many link libraries / objects
2. too long library / object names (paths)
3. too many unncessary library paths
4. too long library paths

#1 we can't change, you can't just leave out some libraries, #2 can be tweaked like you did.
However, #3 and #4 might be worth being looked into.
Do you have any long linker paths set up in compiler options which are not strictly necessary? It is because I have none, and for me it works, so that might just be it. Apart from that, I'll look into the project to see whether there is something that can be left out.

#3 - developers error, we have no reasons to look it. Developer may correct this error.
#1,2,4 - may being resolved with linker scripts (see ld help). If not, in future this problem will wake up.

I use standart way for the IBM VisualAge C++ compiler.

Look example for Makefile (fragment only):
Code
$(TARGET1): $(OBJS1)
    @echo " Link "
    icc.exe /Q+ @<<
     /B" /NOL $(LINKDEB)"
     /Fe$(TARGET1) 
     $**
<<

Here nmake expand it with a this command lines:
Code
echo " Link "
icc.exe /Q+ @C:\Temp\65000000.CTN.
del C:\Temp\65000000.CTN.

File C:\Temp\65000000.CTN content list of options and objects for linker.
In this hand, we have not problem with command line limit.
I yet no look a help info for mingw32-make.xe, may be the mingw make have other methods. Who knows.
Title: Re: wxScintilla build error on HEAD
Post by: tiwag on December 07, 2005, 12:58:49 pm
@therion
very interesting phenomen - i'm working with WinXP_SP2 and it doesn't appear

even though my linker command-string for wxscintilla is 4528 characters long - your's is shorter,
because you are using a shorter WX_DIR than i.  ( your "C:\wx" compared to my "D:\wx261" )

i have enlarged the command-shell environment ram to about 12kB,
but this should not really affect the max. size of the command-line,
but who knows ?

btw. what's your OS ?

[edited typos]
Title: Re: wxScintilla build error on HEAD
Post by: thomas on December 07, 2005, 01:12:29 pm
Yes, linker scripts or incremental linking might help out. But those are all nasty hacks, we have no guarantee that they work with all linkers.
The preferrable way of solving the problem would be to reduce the redundancy in path names, and the easiest way to do that would be to move the obj paths into the respective targets' directories rather than keeping all objects in one folder.
Title: Re: wxScintilla build error on HEAD
Post by: therion on December 07, 2005, 01:13:32 pm
Hello tiwag :-)

humm, really interesting, im using w2k sp4...
another wierd thing is that the patch thomas has just commited didn't work for me (rev 1461).

don't know... :-/
Title: Re: wxScintilla build error on HEAD
Post by: kisoft on December 07, 2005, 01:44:29 pm
To thomas:
I spoke about build CodeBlocks, no all other compilers. Only MinGW. Only Win platform.
I mean *nix have no this problem.

To therion:
My method don't help?
Title: Re: wxScintilla build error on HEAD
Post by: mandrav on December 07, 2005, 01:50:10 pm
This is a known limitation of command.com environment size in Win95/Win98. Increase your environment size...
Title: Re: wxScintilla build error on HEAD
Post by: therion on December 07, 2005, 02:23:32 pm
Quote from: mandrav on December 07, 2005, 01:50:10 pm
This is a known limitation of command.com environment size in Win95/Win98. Increase your environment size...

Hello mandrav and kisoft :-)

I use win2k sp4...

I don't know i made myself clear (sorry, english is not my native language) but the point is:
- using HEAD sources (1462 at the moment)
- if i open these sources inside a "cb 1421", i can build anything...
- if i open te same same sources on a "newer cb" i get this error.

IMHO:
- the machine, OS, compiler (gcc3.4.4) etc are the same, so there is no problem.
- the sources are the same (HEAD).
- the IDEs used to build are different: on a 1421 it works, on a newer it DOESNT.

I don't know... something was changed during the weekend (between 1421 and 1447, i dont know when) that is causing this problem for me...

kisoft: yes it works :-) but...
Title: Re: wxScintilla build error on HEAD
Post by: mandrav on December 07, 2005, 02:50:42 pm
Quote from: therion on December 07, 2005, 02:23:32 pm
IMHO:
- the machine, OS, compiler (gcc3.4.4) etc are the same, so there is no problem.
- the sources are the same (HEAD).
- the IDEs used to build are different: on a 1421 it works, on a newer it DOESNT.

I don't know... something was changed during the weekend (between 1421 and 1447, i dont know when) that is causing this problem for me...

Sorry, I hadn't seen you mentioned win2k.
Anyway, nothing's changed regarding wxScintilla in those revisions. It was updated to a later version maybe but that was code that changed, not files...
And besides, wouldn't we all have problems?
Strange this one...
Title: Re: wxScintilla build error on HEAD
Post by: therion on December 07, 2005, 02:56:50 pm
yes... very strange... ill check out other revisions to find out exactly on which one it happened...
but anyway, there is nothing wrong with scintilla, it builds perfectly if i use the ide rev1421, the problem is with the "build system"...

Title: Re: wxScintilla build error on HEAD
Post by: kisoft on December 07, 2005, 03:04:09 pm
To therion:

A simple way - compare command line for link on rev1421 and last.
Title: Re: wxScintilla build error on HEAD
Post by: therion on December 07, 2005, 03:06:16 pm
errrrr (really) stupid question: how? :-P
Title: Re: wxScintilla build error on HEAD
Post by: mandrav on December 07, 2005, 03:08:09 pm
Update now, build it and try if it works. I think we found the reason...
EDIT: kudos to Thomas for giving me a hint :)
Title: Re: wxScintilla build error on HEAD
Post by: therion on December 07, 2005, 03:15:40 pm
its building right now.... thanks mandrav, ill tell you the results in a moment :-)
anyway, is there an option to i enable the command line tracing? if so, where is it?
Title: Re: wxScintilla build error on HEAD
Post by: mandrav on December 07, 2005, 03:17:29 pm
If you mean you want to see the actual build commands, go to "Settings->Compiler->Other" and set to "Full logging".
Title: Re: wxScintilla build error on HEAD
Post by: therion on December 07, 2005, 03:25:58 pm
Yessssssss!!!!!! Thats it, fully working again!!!!!
Youre the man mandrav  :lol:

Thanks,

Title: Re: wxScintilla build error on HEAD
Post by: kisoft on December 07, 2005, 04:08:12 pm
To mandrav:

Ok, all right!

Hmm, removed "cmd.exe /c", I must look this windoze or wxExecute feature.
"It would be interesting to know what happened."