Update of bug #25528 (project gnustep):
Status: Need Info = Fixed
Open/Closed:Open = Closed
___
Follow-up Comment #16:
I close this bug
Follow-up Comment #8, bug #25528 (project gnustep):
Great news ... if it's a 64bit problem then it's almost certainly not in the
code I added to NSImage.m, but rather in the invocation code ... and tracking
it down/fixing it is likely to cure other subtle bugs.
Update of bug #25528 (project gnustep):
Status:None = Need Info
___
Follow-up Comment #9:
OK, I really, really, really need to know how to reproduce this. I dug out
my old 64bit
Follow-up Comment #10, bug #25528 (project gnustep):
I'm not sure what's going on then because all I'm doing is a clean build and
starting applications on my debian-etch box and seeing the issue straight
away. There are no steps to reproduce it. I will try to do another clean
build to see if
Follow-up Comment #11, bug #25528 (project gnustep):
For comparison, my machine where things are working fine is debian unstable
(though not updated or a while) with the 2.6.26-1-amd64 kernel.
Since suspicion about proxies falls on the invocation system ...
things are compiled with gcc-4.3.3
Follow-up Comment #12, bug #25528 (project gnustep):
okay... one thing I have noticed is that I am using GNUstep's Window
decorations. The close and miniaturize icons are missing.
Also on the save panel the disk and other images near the buttons are missing
including the return symbol on the
Follow-up Comment #13, bug #25528 (project gnustep):
I am using ffcall and not libffi. Should this make a difference?
___
Reply to this item at:
http://savannah.gnu.org/bugs/?25528
___
Follow-up Comment #14, bug #25528 (project gnustep):
This appears to be the issue. The images are present when using libffi
instead of ffcall. I'm wondering, since ffcall is deprecated, if it's even
worth looking into this problem.
The issue doesn't seem to be present on older systems where
Follow-up Comment #15, bug #25528 (project gnustep):
Well one option would simply be to modify configure.ac to set ffcall to be
known not to work on your hardware/os, so that people will have to use
libffi.
That means setting do_broken_ffcall=yes etc, as already done for sparc64
solaris.
