|
From: ColdShine <col...@us...> - 2008-08-29 21:18:35
|
Let me rephrase the problem: is there any known issue/ bug/ misbehavior/ unproper environment configuration which would cause windres to complain about line 1 of *any* file? 2008/8/29 Greg Chicares <gch...@sb...>: > > /tmp[0]$touch empty.rc > /tmp[0]$windres -v -i empty.rc -o empty.res > Using `gcc -E -xc -DRC_INVOKED empty.rc' > Using popen to read preprocessor output > windres: no resources > /tmp[1]$windres --version |head -1 > GNU windres 2.17.50 20060817 Oh, I do believe this works, normally. I just can't figure not even a single reason this would not want to work on my system. Actually I realize now I forgot to mention something: C:\Profiles\ColdShine>windres -V GNU windres 2.17.50 20060824 So apparently I'm working on a slightly newer version. I don't think that's what makes the difference, though. And, for what matters: C:\Profiles\ColdShine>gcc --version gcc (GCC) 3.4.5 (mingw special) And my OS is Windows XP Professional. Profiles is my "Document and Settings" folder. I gave it a shorter and spaceless name using an altered Windows XP Pro installation disc. MinGW is installed in C:\Programs\MinGW and MSYS is in C:\Programs\MSys. I manually set %Path% to include MinGW\bin and MSys\bin (in this order). The error is entirely windres-dependant, as invoking it from cmd.exe or MSys's sh yields the very same results. >> Anyway, in case you still don't feel like relying on my statement > > It's not a personal matter of believing your report or not. Rather, > it's an objective matter of finding out how to reproduce the problem. I know, but tests I've done by myself already demonstrate my problem is totally unrelated to the file being processed, hence the only explanation to Chris's request would be he didn't want to rely on them. I seem to understand the problem, exposed the way I did, is as cryptic to experts just as much as it is for me. Let me rephrase the problem, then: <moved to head of this message>. Anyway, I just downloaded the windres (GNU binutils) source code. If I'm able to compile it, I'll just stuff it with fprintf stderr (no debugger yet - waiting to learn GDB - it's a new computer I want to keep from running non-free software except Windows) to find out why it's complaining. Then I'll probably bang my head on the keyboard for this oh-so-trivial mistake I did which I can't even get to figure. Thank you too. CS |