Hello everybody,
as I'm running into the well-known "gnuplot-inkscape"-bug of 0.46, and unluckily no 0.47 ppc precompiled packages are available, I tried to compile the most recent package myself on Mac OS X 10.4.11 PPC.
After "./configure" I run into this error message:
configure: error: libpng >= 1.2 is needed to compile inkscape
But I do have a suitable libpng:
port installed libpng The following ports are currently installed: libpng @1.2.38_0 (active)
So this may be a path issue - I googled that several people had this problem as well, but couldnt find how to resolve it.
Any hint would be appreciated.
Greetings,
Wolf
On 7/11/09 11:55, Wolf Drechsel wrote:
as I'm running into the well-known "gnuplot-inkscape"-bug of 0.46, and unluckily no 0.47 ppc precompiled packages are available, I tried to compile the most recent package myself on Mac OS X 10.4.11 PPC.
After "./configure" I run into this error message:
configure: error: libpng >= 1.2 is needed to compile inkscape
But I do have a suitable libpng:
port installed libpng The following ports are currently installed: libpng @1.2.38_0 (active)
Initially when running autogen.sh and configure on OS X 10.5.8 i386 I had the same issue. My workaround at that time is described in an earlier thread [1], but as I lack experience and coding skills myself I can't judge its validity. Maybe one of devs involved in the osx packaging process can provide more insight into this problem.
~suv
[1] http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/31219/focus=31221
Hello ~suv,
thanks for your reply.
Sorry that I'm really a kid… - I assumed that the sentence "and after adding the PKG_CONFIG_PATH to the shell environment" means pasting
export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"
into the shell - and than do autogen, configure, make and make install.
So did I - but ended up with the same error. Or should I have copied the line into one of the files?
Greetings,
Wolf
On 7/11/09 11:55, Wolf Drechsel wrote:
as I'm running into the well-known "gnuplot-inkscape"-bug of 0.46, and unluckily no 0.47 ppc precompiled packages are available, I tried to compile the most recent package myself on Mac OS X 10.4.11 PPC.
After "./configure" I run into this error message:
configure: error: libpng >= 1.2 is needed to compile inkscape
But I do have a suitable libpng:
port installed libpng The following ports are currently installed: libpng @1.2.38_0 (active)
Initially when running autogen.sh and configure on OS X 10.5.8 i386 I had the same issue. My workaround at that time is described in an earlier thread [1], but as I lack experience and coding skills myself I can't judge its validity. Maybe one of devs involved in the osx packaging process can provide more insight into this problem.
~suv
[1] <http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/31219/ focus=31221>
On 7/11/09 14:06, Wolf Drechsel wrote:
On 7/11/09 13:50, ~suv wrote:
On 7/11/09 11:55, Wolf Drechsel wrote:
as I'm running into the well-known "gnuplot-inkscape"-bug of 0.46, and unluckily no 0.47 ppc precompiled packages are available, I tried to compile the most recent package myself on Mac OS X 10.4.11 PPC.
After "./configure" I run into this error message:
configure: error: libpng >= 1.2 is needed to compile inkscape
But I do have a suitable libpng:
port installed libpng The following ports are currently installed: libpng @1.2.38_0 (active)
Initially when running autogen.sh and configure on OS X 10.5.8 i386 I had the same issue. My workaround at that time is described in an earlier thread [1], but as I lack experience and coding skills myself I can't judge its validity. Maybe one of devs involved in the osx packaging process can provide more insight into this problem.
[1] http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/31219/focus=31221
Sorry that I'm really a kid… - I assumed that the sentence "and after adding the PKG_CONFIG_PATH to the shell environment" means pasting
export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"
into the shell - and than do autogen, configure, make and make install.
So did I - but ended up with the same error. Or should I have copied the line into one of the files?
In the previous posting in that thread I described that I put the shell environment configuration [2] into a shell script which I source whenever I need the build environment set up (e.g. to run configure):
contents of config-env.sh: #<--- snip ---> #!/bin/sh
export LIBPREFIX="/opt/local" # automake seach path export CPATH="$LIBPREFIX/include" # configure search path export CPPFLAGS="-I$LIBPREFIX/include" export LDFLAGS="-L$LIBPREFIX/lib" # compiler arguments export CFLAGS="-O3 -Wall" export CXXFLAGS="$CFLAGS" # to speed up the compilation export CC="ccache gcc" export CXX="ccache g++"
export ACLOCAL_FLAGS="-I $LIBPREFIX/share/aclocal" export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"
#eof #<--- snip --->
But please note that I am not sure if this is the correct way to handle the issue - in one of my other posts in that previous thread I mention that the MacPorts inkscape-devel port [3] includes a set of patches for autogen.sh and configure that possibly address a similar problem with a proper solution... I never tried to make use of those patches and I never build inkscape-devel via MacPorts (only the needed dependencies to build Inkscape.app outside of MacPorts).
~suv (I know that's not very helpful, but it's all I know ATM)
[2] the build environment variables as mentioned on the Wiki page about building Inkscape on OS X. http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX#Setting_the_build_environment
[3] inkscape-devel Portfile: http://trac.macports.org/browser/trunk/dports/graphics/inkscape-devel/Portfile Patches in the files subdirectory: http://trac.macports.org/browser/trunk/dports/graphics/inkscape-devel
Or should I have copied the line into one of the files?
In the previous posting in that thread I described that I put the shell environment configuration [2] into a shell script which I source whenever I need the build environment set up (e.g. to run configure):
This is precisely what osx-build.sh (in packaging/macosx/) is there for. Would you care to comment on why you don't use it?
If you find that it gets outdated, please report it (not necessarily a full blown bug report but an email will be enough to start with). Now if I follow correctly, you are suggesting that
export ACLOCAL_FLAGS="-I $LIBPREFIX/share/aclocal" export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"
should be added to osx-build.sh right? Wolf, if you could test whether that solves the problem on your system, tht would be nice. If it does, I'll add to once the trunk is reopened.
JiHO --- http://maururu.net
On 7/11/09 21:56, JiHO wrote:
Or should I have copied the line into one of the files?
In the previous posting in that thread I described that I put the shell environment configuration [2] into a shell script which I source whenever I need the build environment set up (e.g. to run configure):
This is precisely what osx-build.sh (in packaging/macosx/) is there for. Would you care to comment on why you don't use it?
Sorry if I don't use these scripts whenever I update from SVN. I ran the autogen.sh/configure script quite some time ago, but since then I didn't make a fresh checkout nor build from a released src package. Therefore I have used neither autogen.sh nor configure lately and didn't research an issue I had encountered with my first build attempts when I tried to follow the wiki page step by step (skipping the first 'For the impatient' section and using the 'recommended' instructions).
<off-topic> When updating from SVN or testing patches I usually don't need to run osx-build.sh because locally I have linked inkscape-bin to 'src/inkscape' (as well as some of the resources inside the bundle to the corresponding subdirectories in 'src/Build/share/inkscape').
Due to an unsolved bug in MacPorts 1.8.x I haven't been able to update the MacPorts dependencies since its upgrade to 1.8 which entailed same basic changes to all portfiles that make them incompatible with older 'port' builds. Because of this I currently do not 'need' to re-bundle newer libraries or resource files for gtk+ and the rest.
Once this bug in MacPorts is fixed (hopefully 1.8.2) I will again build the full app regularly and try to report back any issues I encounter. </off-topic>
If you find that it gets outdated, please report it (not necessarily a full blown bug report but an email will be enough to start with). Now if I follow correctly, you are suggesting that
export ACLOCAL_FLAGS="-I $LIBPREFIX/share/aclocal" export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"
should be added to osx-build.sh right? Wolf, if you could test whether that solves the problem on your system, tht would be nice. If it does, I'll add to once the trunk is reopened.
Going again through my old logs from the first attempts to build inkscape because I can't remember the details... roughly these are the steps I took (as fair as I can reconstruct it now):
source ../config_build.sh ### set build environment ./autogen.sh ### failed, after setting $ACLOCAL_FLAGS succeeded cd packaging/macosx ./osx-build.sh c ### failed (libpng), $PKG_CONFIG_PATH didn't help cd ../.. ./configure --enable-osxapp \ --prefix=/path/to/inkscape/packaging/macosx/../../Build/ ### configure succeeded, likely that $PKG_CONFIG_PATH helped (not verified) cd packaging/macosx ./osx-build.sh p -py /path/to/Python-packages
Looking at this now it seems that the mix (src/autogen.sh and packaging/macosx/osx-build.sh) didn't work (my mistake) i.e. once I started with ./autogen.sh I needed to follow with ./configure using the correct configure flags copied from osx-build.sh. But honestly I am afraid that drawing this conclusion without re-testing isn't correct either ;-)
Yet it most likely means that the build scripts in 'packaging/macosx' don't need to be updated.
@ Wolf - sorry, AFAICT now my tips are wrong and you better stick to using the build scripts in 'packaging/macosx' only and don't run autogen.sh/configure by itself.
@JiHO - I'll try next week to build a fresh checkout or 0.47pre4 strictly using your scripts (without updating the MacPorts tree first) and report back if I encounter any errors.
~suv (who shouldn't have answered without re-checking the build logs!)
This is precisely what osx-build.sh (in packaging/macosx/) is there for. Would you care to comment on why you don't use it?
Hello men,
sorry for answering so late.
And another sorry for not facing the challenge of another compiling orgy, as I see it's quite complicated, and I found a workaround for my problem. I'll keep to the aqua thing…
But maybe all your work and effort is not lost, probabely ~suv and I ran into the same trap:
As Mac people like to have things very easy, we can easily get lost if there is a clear instruction. So, if a Maccie reads the README (yes, some Maccies do so…), he finds:
Inkscape uses the standard procedure for compilation and installation:
./configure make make install
If a "./configure" file is not present, you can create it by running the "./autogen.sh" command, which calls in turn a number of other programs such as automake and autoconf. See INSTALL for more details.
At this point I forgot that on a Mac there is much more about it - allthough I fought myself all the way to an inkscape aquaalpha… - So it might be helpful to add a sentence like "Mac OS X users please have a close look at the wiki pages under http://wiki.inkscape.org/ wiki/index.php/CompilingMacOsX. You should use macports to make it work… etc"
Thanks for your support - looking forward to 0.47 anyways!
Greetings,
Wolf
On 7/11/09 21:56, JiHO wrote:
Or should I have copied the line into one of the files?
In the previous posting in that thread I described that I put the shell environment configuration [2] into a shell script which I source whenever I need the build environment set up (e.g. to run configure):
This is precisely what osx-build.sh (in packaging/macosx/) is there for. Would you care to comment on why you don't use it?
If you find that it gets outdated, please report it (not necessarily a full blown bug report but an email will be enough to start with). Now if I follow correctly, you are suggesting that
export ACLOCAL_FLAGS="-I $LIBPREFIX/share/aclocal" export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"
should be added to osx-build.sh right? Wolf, if you could test whether that solves the problem on your system, tht would be nice. If it does, I'll add to once the trunk is reopened.
I tested with a fresh checkout (rev 22575), using exclusively osx-build.sh to configure/build/install/package/distribute in single steps.
A - autogen.sh failure
1) autogen fails ($ ./osx-build.sh a) log attached, fixed by applying the patch from MacPorts [1]
2) configure: ok ($ ./osx-build.sh c)
3) build: ok ($ ./osx-build.sh b)
4) install: ok ($ ./osx-build.sh i)
5) package: ok ($ ./osx-build.sh p -py /local/path/to/Python-packages) error to rewrite dylb paths because I'm using the old MacPorts tree
6) distribute: ok ($ ./osx-build.sh d)
Conclusion: on Leopard 1.5.8 the patch for autogen.sh from MacPorts works. If this can be confirmed for other OS X versions as well as other linux and unix systems maybe the patch could be committed to the trunk?
[1] http://trac.macports.org/browser/trunk/dports/graphics/inkscape-devel/files/patch-autogen.sh.diff
B - internal perl/python
I tested the second patch from MacPorts for configure.ac, but internal Python support (--with-python) never succeeded to configure when 'checking for Python development environment'. Internal Perl support (--with-perl) however was configured without error. Since both options are skipped per default of 'osx-build.sh' and the script console has been disabled for 0.47 anyway I didn't further investigate where the mistake is (missing py25/py26 dependencies?) or whether the patch is needed at all for Inkscape 0.47.
C - System Info
Mac OS X 10.5.8 (9L30) $ uname -a Darwin LeWitt.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 MacPorts 1.7.1 ('port installed' attached) LIBPREFIX="/Volumes/blue/mp"
Note: currently the bundles I create still have to use DYLD_LIBRARY_PATH.
hth, ~suv
LeWitt:macosx suv$ ./osx-build.sh u At revision 22575. LeWitt:macosx suv$ ./osx-build.sh a ============================================================================= When you report a trouble about building SVN version of inkscape, Please report following information about distro and tools version, too.
--1. distribution------------------------------------------------------------ -e distro: Cannot find distribution information Terminating....
--2. tools------------------------------------------------------------------- -n /usr/bin/m4: -n /Volumes/blue/mp/bin/autoconf: autoconf (GNU Autoconf) 2.64 -n /Volumes/blue/mp/bin/autoheader: autoheader (GNU Autoconf) 2.64 -n /Volumes/blue/mp/bin/automake: automake (GNU automake) 1.11 automake-1.7: not found automake-1.8: not found automake-1.9: not found -n /Volumes/blue/mp/bin/aclocal: aclocal (GNU automake) 1.11 aclocal-1.7: not found aclocal-1.8: not found aclocal-1.9: not found -n /Volumes/blue/mp/bin/intltoolize: intltoolize (GNU intltool) 0.40.6 -n /Volumes/blue/mp/bin/gettextize: /Volumes/blue/mp/bin/gettextize (GNU gettext-tools) 0.17
--3. environment variables--------------------------------------------------- LDFLAGS=-L/opt/local/lib MANPATH=/Volumes/blue/mp/share/man:/Volumes/blue/local/man:/usr/share/man:/usr/local/share/man:/usr/X11/share/man CPPFLAGS=-I/opt/local/include CPATH=/opt/local/include CXXFLAGS=-O3 -Wall PATH=/Volumes/blue/mp/bin:/Volumes/blue/mp/sbin:/Volumes/blue/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin LANG=en_US.UTF-8 CFLAGS=-O3 -Wall
=============================================================================
I am testing that you have the required versions of autoconf, automake, glib-gettextize and intltoolize. This test is not foolproof and if anything goes wrong, there may be guidance in the file HACKING.txt
checking for autoconf >= 2.52 ... yes (version 2.64) checking for automake >= 1.10 ... yes (version 1.10) checking for glib-gettextize >= 2.0.0 ... yes (version 2.20.4) checking for intltool >= 0.17 ... yes (version 0.40.6)
WARNING: aclocal's directory is /usr/share/aclocal, but... no file /usr/share/aclocal/glib-2.0.m4 You may see fatal macro warnings below. If these files are installed in /some/dir, set the ACLOCAL_FLAGS environment variable to "-I /some/dir", or install /usr/share/aclocal/glib-2.0.m4.
WARNING: aclocal's directory is /usr/share/aclocal, but... no file /usr/share/aclocal/glib-gettext.m4 You may see fatal macro warnings below. If these files are installed in /some/dir, set the ACLOCAL_FLAGS environment variable to "-I /some/dir", or install /usr/share/aclocal/glib-gettext.m4.
WARNING: aclocal's directory is /usr/share/aclocal, but... no file /usr/share/aclocal/gtk-2.0.m4 You may see fatal macro warnings below. If these files are installed in /some/dir, set the ACLOCAL_FLAGS environment variable to "-I /some/dir", or install /usr/share/aclocal/gtk-2.0.m4.
WARNING: aclocal's directory is /usr/share/aclocal, but... no file /usr/share/aclocal/intltool.m4 You may see fatal macro warnings below. If these files are installed in /some/dir, set the ACLOCAL_FLAGS environment variable to "-I /some/dir", or install /usr/share/aclocal/intltool.m4.
WARNING: aclocal's directory is /usr/share/aclocal, but... no file /usr/share/aclocal/pkg.m4 You may see fatal macro warnings below. If these files are installed in /some/dir, set the ACLOCAL_FLAGS environment variable to "-I /some/dir", or install /usr/share/aclocal/pkg.m4.
Running aclocal-1.10 ... configure.ac:133: warning: macro `AM_GLIB_GNU_GETTEXT' not found in library Running autoheader ... autoheader: warning: missing template: ENABLE_NLS autoheader: Use AC_DEFINE([ENABLE_NLS], [], [Description]) Please fix the error conditions and try again.
autogen failed
The following ports are currently installed: apache2 @2.2.11_0+darwin_9 (active) apr @1.3.7_0 apr @1.3.8_0 (active) apr-util @1.3.8_0 apr-util @1.3.9_0 (active) aspell @0.60.6_2+macosx (active) aspell-dict-de @20030222_0 (active) aspell-dict-en @6.0_0 (active) atk @1.26.0_1 (active) audiofile @0.2.6_2 (active) autoconf @2.64_0 autoconf @2.64_2 (active) autoconf213 @2.13_1 (active) automake @1.11_0 (active) bison @2.4.1_0 (active) boehmgc @7.1_0+darwin_9 (active) boost @1.39.0_2 (active) boost-jam @3.1.17_0 (active) bzip2 @1.0.5_2 (active) cairo @1.8.8_0+macosx (active) cairomm @1.8.2_0 (active) ccache @2.4_2 (active) cyrus-sasl2 @2.1.23_0+kerberos (active) db46 @4.6.21_5 (active) dbus @1.2.14_0+no_root+no_startupitem (active) dbus-glib @0.80_0 (active) desktop-file-utils @0.15_1 (active) dia @0.97_0 (active) docbook-xml @5.0_0 (active) docbook-xml-4.1.2 @4.1.2_1 (active) docbook-xml-4.2 @4.2_0 (active) docbook-xml-4.3 @4.3_0 (active) docbook-xml-4.4 @4.4_0 (active) docbook-xml-4.5 @4.5_0 (active) docbook-xml-5.0 @5.0_0 (active) docbook-xsl @1.75.1_0 docbook-xsl @1.75.2_0 (active) enchant @1.5.0_0 (active) esound @0.2.41_1 (active) expat @2.0.1_0 (active) fftw-3 @3.2.2_0 (active) fontconfig @2.7.0_0+macosx fontconfig @2.7.1_0+macosx (active) freetype @2.3.9_0+macosx (active) gawk @3.1.7_0 (active) gconf @2.26.2_0+no_polkit (active) gd2 @2.0.35_5 (active) gdbm @1.8.3_1 (active) getopt @1.1.4_1 (active) gettext @0.17_4 (active) ggv @2.12.0_0 (active) ghostscript @8.64_3 ghostscript @8.70_0 (active) giflib @4.1.6_1 (active) glib2 @2.20.4_0 (active) glibmm @2.20.1_0 (active) gnome-common @2.26.0_0 (active) gnome-doc-utils @0.16.1_0 gnome-doc-utils @0.16.1_1 (active) gnome-icon-theme @2.26.0_0 (active) gnome-keyring @2.26.3_0 (active) gnome-mime-data @2.18.0_3 (active) gnome-vfs @2.24.1_0 (active) gnutls @2.6.5_0 gnutls @2.8.3_0 (active) gperf @3.0.4_0 (active) graphviz @2.24.0_0+macosx+perl+rsvg (active) gsed @4.2.1_0 (active) gsl @1.12_0 (active) gtk-doc @1.11_0 gtk-doc @1.11_1 (active) gtk-engines2 @2.18.2_0 (active) gtk2 @2.16.4_0+x11 gtk2 @2.16.5_0+x11 (active) gtk2-clearlooks @0.6.2_0 (active) gtk2-murrine @0.90.3_0 (active) gtkmm @2.16.0_0 (active) gtkspell2 @2.0.15_0 (active) gv @3.6.7_0 (active) help2man @1.36.4_1 (active) hicolor-icon-theme @0.10_0 (active) hunspell @1.2.8_0 (active) icon-naming-utils @0.8.90_0 (active) ImageMagick @6.5.4-0_0+graphviz+gs+jbig+jpeg2+lcms+mpeg+perl+q16+rsvg+wmf ImageMagick @6.5.5-0_0+graphviz+gs+jbig+jpeg2+lcms+mpeg+perl+q16+rsvg+wmf (active) imake @1.0.2_1 (active) intltool @0.40.6_0 (active) iso-codes @3.10.1_0 iso-codes @3.10.2_0 (active) jasper @1.900.1_4 (active) jbigkit @2.0_0 (active) jpeg @6b_3 (active) lcms @1.18a_0 (active) libart_lgpl @2.3.20_0 (active) libbonobo @2.24.1_0 (active) libbonoboui @2.24.1_0 (active) libcroco @0.6.2_0 (active) libemf @1.0.3_0 (active) libgcrypt @1.4.4_0 (active) libglade2 @2.6.4_0 (active) libgnome @2.26.0_0 (active) libgnomecanvas @2.26.0_0 (active) libgnomecups @0.2.3_1 (active) libgnomeprint @2.18.6_0 (active) libgnomeprintui @2.18.4_0 (active) libgnomeui @2.24.1_0 (active) libgpg-error @1.7_0 (active) libgsf @1.14.15_0 (active) libiconv @1.13_0 (active) libidl @0.8.13_0 (active) libpixman @0.14.0_0 (active) libpng @1.2.38_0 (active) librsvg @2.26.0_0 librsvg @2.26.0_1 (active) libsigcxx2 @2.2.3_0 libsigcxx2 @2.2.4_0 (active) libtasn1 @1.7_0 libtasn1 @2.2_0 (active) libtool @2.2.6a_0 (active) libwmf @0.2.8.4_2 (active) libwpd @0.8.14_0 (active) libwpg @0.1.3_0 (active) libxml2 @2.7.3_0 (active) libxslt @1.1.24_2 (active) loudmouth @1.4.3_0 (active) lzmautils @4.32.7_1 (active) lzo @1.08_0 (active) m4 @1.4.13_0 (active) mhash @0.9.9.9_0 (active) mpeg2vidcodec @1.2_3 (active) ncurses @5.7_0 (active) ncursesw @5.7_0 (active) neon @0.28.4_0 neon @0.28.6_0 (active) opencdk @0.6.6_0 (active) openjpeg @1.3_3 (active) openssl @0.9.8k_0 (active) orbit2 @2.14.17_0 orbit2 @2.14.17_1 (active) p5-getopt-long @2.38_0 (active) p5-locale-gettext @1.05_0 (active) p5-pathtools @3.29_0 (active) p5-scalar-list-utils @1.19_1 (active) p5-xml-namespacesupport @1.10_0 (active) p5-xml-parser @2.36_0 (active) p5-xml-sax @0.96_1 (active) p5-xml-simple @2.18_0 (active) pango @1.24.5_0+macosx (active) pangomm @2.24.0_0 (active) pcre @7.9_0 (active) perl5 @5.8.9_0 (active) perl5.8 @5.8.9_3 (active) php5 @5.3.0_1+apache2+macosx php5 @5.3.0_2+apache2+macosx (active) pkgconfig @0.23_1 (active) plotutils @2.5_0 (active) poppler @0.11.1_0 (active) poppler-data @0.2.1_0 (active) popt @1.15_0 (active) port_cutleaves @0.1.1_0 (active) pstoedit @3.45_3 (active) py25-libxml2 @2.6.21_1 (active) py25-lxml @2.2.2_0 (active) py25-nose @0.10.4_0 (active) py25-numeric @24.2_1+macosx (active) py25-numpy @1.3.0_0 (active) py25-pil @1.1.6_0 (active) py25-reportlab @2.3_1 (active) py25-setuptools @0.6c9_0 (active) py26-libxml2 @2.6.21_0 (active) py26-lxml @2.2.2_0 (active) py26-nose @0.10.4_0 py26-nose @0.11.1_0 (active) py26-numeric @24.2_0+macosx (active) py26-numpy @1.3.0_0 (active) py26-pil @1.1.6_0 (active) py26-reportlab @2.3_0 (active) py26-setuptools @0.6c9_0 (active) python25 @2.5.4_6+darwin_9+macosx (active) python26 @2.6.2_3 python26 @2.6.2_4 (active) python_select @0.2.1_0+darwin_9 (active) rarian @0.8.1_0 (active) readline @6.0.000_1 (active) ruby @1.8.7-p174_0+thread_hooks (active) serf @0.3.0_0 (active) shared-mime-info @0.60_0 (active) sqlite3 @3.6.16_0 sqlite3 @3.6.17_0 (active) subversion @1.6.3_0 subversion @1.6.4_0 subversion @1.6.5_0 (active) swig @1.3.39_1+perl+php5+python+ruby swig @1.3.40_0+perl+php5+python+ruby (active) tcl @8.5.6_0 (active) texinfo @4.13_0 (active) tiff @3.8.2_3+macosx (active) tk @8.5.6_1 (active) urw-fonts @1.0.7pre44_0 (active) Xaw3d @1.5E_4 (active) Xft2 @2.1.13_1 Xft2 @2.1.13_2 (active) xmlcatmgr @2.2_1 (active) xorg-bigreqsproto @1.0.2_0 (active) xorg-cf-files @1.0.2_3 (active) xorg-compositeproto @0.4_0 (active) xorg-damageproto @1.1.0_0 (active) xorg-fixesproto @4.0_0 xorg-fixesproto @4.1_0 (active) xorg-inputproto @1.5.1_0 (active) xorg-kbproto @1.0.3_0 (active) xorg-libice @1.0.5_0 xorg-libice @1.0.5_1 (active) xorg-libsm @1.1.0_0 xorg-libsm @1.1.0_1 xorg-libsm @1.1.1_0 (active) xorg-libX11 @1.2.2_0 (active) xorg-libXau @1.0.4_0 xorg-libXau @1.0.4_1 (active) xorg-libXaw @1.0.6_0 (active) xorg-libXcomposite @0.4.0_0 xorg-libXcomposite @0.4.0_1 (active) xorg-libXcursor @1.1.9_0 xorg-libXcursor @1.1.9_1 (active) xorg-libXdamage @1.1.1_0 xorg-libXdamage @1.1.1_1 (active) xorg-libXdmcp @1.0.2_0 xorg-libXdmcp @1.0.2_1 (active) xorg-libXext @1.0.5_1 xorg-libXext @1.0.99.4_1 (active) xorg-libXfixes @4.0.3_0 xorg-libXfixes @4.0.3_1 (active) xorg-libXi @1.2.1_0 xorg-libXi @1.2.1_1 (active) xorg-libXinerama @1.0.3_0 xorg-libXinerama @1.0.3_1 (active) xorg-libXmu @1.0.4_0 xorg-libXmu @1.0.4_1 (active) xorg-libXp @1.0.0_2 xorg-libXp @1.0.0_3 (active) xorg-libXrandr @1.3.0_0 xorg-libXrandr @1.3.0_1 (active) xorg-libXScrnSaver @1.1.3_0 xorg-libXScrnSaver @1.1.3_1 xorg-libXScrnSaver @1.2.0_0 (active) xorg-libXt @1.0.6_0 (active) xorg-printproto @1.0.4_0 (active) xorg-randrproto @1.3.0_0 (active) xorg-renderproto @0.11_0 (active) xorg-scrnsaverproto @1.1.0_0 xorg-scrnsaverproto @1.2.0_0 (active) xorg-util-macros @1.2.2_0 (active) xorg-xcmiscproto @1.1.2_0 (active) xorg-xextproto @7.0.5_0 xorg-xextproto @7.1.0_0 xorg-xextproto @7.1.1_0 (active) xorg-xf86bigfontproto @1.1.2_0 (active) xorg-xineramaproto @1.1.2_0 (active) xorg-xproto @7.0.15_0 (active) xorg-xtrans @1.2.3_0 xorg-xtrans @1.2.4_0 (active) xpm @3.5.7_0 xpm @3.5.7_1 (active) xrender @0.9.4_5 xrender @0.9.4_6 (active) xv @3.10a_4 (active) zlib @1.2.3_2 (active)
On Sat, Nov 14, 2009 at 21:02, ~suv <suv-sf@...58...> wrote:
Conclusion: on Leopard 1.5.8 the patch for autogen.sh from MacPorts works. If this can be confirmed for other OS X versions as well as other linux and unix systems maybe the patch could be committed to the trunk?
[1] http://trac.macports.org/browser/trunk/dports/graphics/inkscape-devel/files/patch-autogen.sh.diff
OK, that's noted for when the trunk reopens. Thanks a lot for testing all this.
JiHO --- http://maururu.net
participants (3)
-
JiHO
-
Wolf Drechsel
-
~suv