After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 641787 - Gimp 2.7.2 Compile Fails on Windows 7 64bit Using gcc 4.4.5
Gimp 2.7.2 Compile Fails on Windows 7 64bit Using gcc 4.4.5
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: Windows Installer
git master
Other Windows
: Normal blocker
: ---
Assigned To: Jernej Simončič
Jernej Simončič
Depends on:
Blocks:
 
 
Reported: 2011-02-08 00:01 UTC by Partha
Modified: 2012-01-09 08:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Partha 2011-02-08 00:01:09 UTC
Compiling Gimp 2.7.2 on Windows 7 64bit using
gcc version 4.4.5 20101001 (release) [svn/rev.164871 - mingw64/oz] (GCC) 
target: x86_64-win64-mingw32 

I downloaded the nightly tars from ftp://gimptest.flamingtext.com/pub/nightly-tarballs/

While making gimp, I encountered the following error:

main.c:293: warning: assignment from incompatible pointer type
make[4]: *** No rule to make target `gimp-2.7.rc.o`, needed by `gimp-2.7.exe`.
Stop

Note that babl and gegl compile fine.

Thanks,
Partha
Comment 1 Partha 2011-02-08 00:01:57 UTC
I used the component installer since I didn't see a component for making gimp.
Comment 2 Partha 2011-02-12 12:51:39 UTC
Here is a discussion I found on registry.gimp.org
http://registry.gimp.org/node/24873

Here the author of one of the commits claims the error could be because

"That error could be because someone decided that my %-style rules are bad and have to be redone:

http://git.gnome.org/browse/gimp/commit/?id=333dfc7f134df1e092aa44108403...

None of us really bothered to check if the new rules work, and apparently they don't."
Comment 3 LightningIsMyName 2011-02-14 22:34:19 UTC
I recently buit 2.7.1 on windows and I mess a lot with building GIMP on windows (even did it directly from git several times some months ago). I'll try to use the flamingtext nightly builds this weekend, but in order to help me debug this, please provide as much information you can about how did you install mingw/msys (especially if you did a manual installation by downloading the packages instead of using the combined mingw/msys automatic installer).

Also, if you can get a distchek version of the source with that commit reverted, and try it and tell us if it fixes the problem, it'll help a lot! (if you can't do this / don't know how, nevermind and I'll do it myself. But it will definetly save me some time if you do that).
Comment 4 Partha 2011-02-15 10:50:56 UTC
Hi,

I am not sure I can give you a bit by bit detail about my installation
of mingw/msys. Suffice it to say, I installed the 2 separately. I am
not sure there is a 64-bit built installer available. I am able to compile and use the 2 systems fine for other assorted libraries as needed.

As for your request, I did sort of do what you are asking. I removed
all references to generating rc.o object files in all the Makefiles
and I was able to compile 2.7.2 on Windows 7 64-bit as a 64-bit program. Please see my website www.partha.com where I talked about it and put up a
screenshot. :)

Does this help? Let me know if there is anything else I can do.

Thanks for looking into this. I really appreciate it. I hope we can
resolve this soon!.

Thanks again,
Partha
Comment 5 LightningIsMyName 2011-02-15 12:37:24 UTC
Correct me if I'm wrong, but as far as I know the MinGW project itself does not provide tools to build 64-bit executables nativly. Does that mean you used the MinGW-w64 project? (If that is the case, it explains why you didn't use the automated installer I talked about, since it's only available for the 32 bit version in the original mingw project)

I never built with the 64 bit toolset before, It would be an interesting challenge :)

Also, what I meant isn't removing the rules for that file, but something else regarding using a different source for GIMP without that patch. Nevermind - I'll do it myself.

Last note - I haven't encountered that problem on my last linux build. I should try to check and see if it's a windows issue (both 32/64 bit tools) or only a 64 windows bit thing.
Comment 6 Partha 2011-02-16 01:16:38 UTC
Hi,

I said all that above (about the Mingw-w64). :)

There is no Msys 64-bit as far as I know. Yes, I used the MinGW-w64 project.

As for what you meant in terms of "decheckout", yes, I did get it. However, I didn't have time to do that. What I did was show that if you remove the rules for windows resource files, it builds just fine. I put up a screenshot here: http://www.partha.com.

I have been using Linux for a long time (from Redhat 5.0 to Ubuntu 10.04). Wanted to test out out all the stuff I have been using lately on Window 7 and I have to have Gimp. Since I have 8 Gigs of RAM, definitely wanted 64-bit. :)

Thanks for all your help!

Partha
Comment 7 Michael Natterer 2012-01-08 20:51:13 UTC
Does this still happen with current git master?
Comment 8 Partha 2012-01-08 21:32:54 UTC
Nope, had forgotten my report. Anyway, now I am building 2.7.5 without problems using 4.5.4.
Comment 9 André Klapper 2012-01-09 08:38:46 UTC
Glad it works for you now & thanks for the quick feedback. Closing as OBSOLETE.