Review Request: cannot compile qt if kderoot path is too long

[Ralf Habacker]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6483/#review9848
-----------------------------------------------------------

Ship it!


looks good

- Ralf


On Feb. 15, 2011, 1:31 p.m., Wolfgang Rohdewald wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://svn.reviewboard.kde.org/r/6483/
> -----------------------------------------------------------
> 
> (Updated Feb. 15, 2011, 1:31 p.m.)
> 
> 
> Review request for kde-windows.
> 
> 
> Summary
> -------
> 
> On windows, gcc/g++ only take a maximum of 8192 chars for command line arguments. If they get more they will not complain but strange things will happen like compiler segfaulting or gcc misinterpreting the arguments at around position 8192. I did not report this as a gcc bug, maybe somebody else already is registered wherever that can be done. I was using mingw4.
> 
> So emerge.py now first checks - it allows a maximum of 10 chars like in c:\kderoot. This results in command line lengths up to around 7700 (maybe more, this is what I saw).
> 
> I was using kderootsvn which makes gcc die when compiling c:\kderootsvn\download\svn-src\qt\src\3rdparty\sqlite\sqlite3.c, the command line having a length of 8214
> 
> 
> Diffs
> -----
> 
>   /trunk/kdesupport/emerge/portage/libs/qt/qt-4.7.1.20101224.py 1220833 
> 
> Diff: http://svn.reviewboard.kde.org/r/6483/diff
> 
> 
> Testing
> -------
> 
> qt compiles with useShortPathes and a long kderoot
> 
> 
> Thanks,
> 
> Wolfgang
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-windows/attachments/20110215/ab026dc3/attachment.htm