Re: Problem compiling with latest libpng in 2.6.2_rc1
Re: Problem compiling with latest libpng in 2.6.2_rc1
- Subject: Re: Problem compiling with latest libpng in 2.6.2_rc1
- From: robert delius royar <email@hidden>
- Date: Wed, 09 Mar 2011 20:13:38 -0500
- Organization: An Apple OS X end user
- Priority: normal
Wed, 9 Mar 2011 (12:02 -0800 UTC) Jeremy Huddleston wrote:
On Mar 9, 2011, at 04:49, robert delius royar wrote:
I have hit a problem compiling XEmacs 21.5 (beta29) with the latest version of XQuartz X11 from macosforge. I am also sending an email to the XEmacs developers' list about the problem. Here is the error I see:
gcc-4.2 -c -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wpointer-arith -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wdeclaration-after-statement -Wunused-parameter -g -O3 -fno-strict-aliasing -arch i386 -I/opt/local/include -Demacs -I. -I/Users/royar/src/xemacs-hg/src -DHAVE_CONFIG_H -I/opt/X11/include -I/opt/X11/include/freetype2 -I/opt/local/include -I/opt/X11/include glyphs-eimage.c
glyphs-eimage.c: In function 'png_instantiate':
glyphs-eimage.c:985: error: dereferencing pointer to incomplete type
...
They're using long-deprecated / now-removed API from libpng.
I checked to see whether there were any macports libpng leftovers, and there were not any includes in the /opt/local/include hierarchy. The problem appears to be an XEmacs variable typedefed to png_infop.
I am mainly looking for what to say to the XEmacs developers about the Xorg version currently in use so that they can change the source to be compatible with 1.5 (oddly, I was able to compile XEmacs under 2.6.1)
Do you mean 2.6.0?
I think I mean the 2.6.1 beta, sorry, I have installed each of the betas
and release candidates on SL for a while, so it would be whatever you
had for us to test before 2.6.1_rc1.
, and otool -L shows that it was using /opt/X11/lib/libpng15.15.dylib (compatibility version 17.0.0, current version 17.0.0). That compilable version was made on 06 March.
Weird... libpng15.15.dylib was not in 2.6.0... only 1.2 and 1.4 ... If you meant 2.6.1_beta1, then I'm equally puzzled because it contained the same png as rc1...
I think that it was finding the old include files API but linking with
the libpng from the new API. Oddly, the program ran fine.
--
Good people do not need laws to tell them to act responsibly,
while bad people will find a way around the laws.
-Plato
20:07 up 62 days, 6:14, 1 user, load averages: 0.26 0.20 0.16
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden