On 21/11/09 17:23, Wolf Drechsel wrote:
o.k. - I went back to the very beginning, using a freshly unpacked sources directory.
I copied your autogen.sh to the sources root directory (I dont think it will work in the src dir) and did chmod 755.
Sorry, I made a mistake - you are correct, it belongs in the inkscape root directory of the unpacked sources.
Then I tried both (following my records from the first inkscape aqua building session):
Moved to the source root dir, did:
export CC="ccache gcc" export CXX="ccache g++" export LIBPREFIX="/opt/local" export CPATH="$LIBPREFIX/include" export CPPFLAGS="-I$LIBPREFIX/include" export LDFLAGS="-L$LIBPREFIX/lib" export CFLAGS="-O3 -Wall" export CXXFLAGS="$CFLAGS" export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
sudo ./autogen.sh
Your $PATH here is wrong.
I assume you copied that from the Wiki page where it is quoted in the instructions to install a second MacPorts tree (i.e. when configuring, building and installing 'MacPorts-1.x.x'), but *only* for that.
Afterwards you *need* to have '/opt/local/bin' (or wherever your current MacPorts tree is installed for the native build) as the first directory of your path, otherwise you can't configure and build inkscape using the dependencies and buildtools installed in MacPorts. Usually a correct installation of MacPorts either takes care of that by adding it to your '~/.profile' or by informing you that you have to update your $PATH and $MANPATH settings in your shell startup file (be it '~/.profile' or '~/.bash_profile').
Can you open a new terminal window, type 'env' and paste the output into your next reply?
On a second go, I tried:
Moving to the packaging/macosx dir, pasting the export commands from above, and then doing sudo ./osx-build.sh a leads to the same result.
I guess that's because the shell script inherits the wrong $PATH if you explicitly restrict it before running osx-build.sh.
Note: you need the other explicit environment settings *only* if you try to use 'autogen.sh' and 'configure' directly instead of using the osx-build script (which sets those variables for you). i.e. no need to set them separately if you plan to use the packaging scripts ;-)
- Your $PATH certainly does look strange to me - it can't find any
recently installed tools in MacPorts because you haven't added it correctly in your PATH.
I was trying to include these things into the path by adding the directories after amother colon - seemed not to be working… - Can you give me the correct settings?
A correct installation of MacPorts takes care of that - there's no need to add additional subdirectories of '/opt/local' to your $PATH - see above.
It is really best to use the scripts in 'packaging/macosx' to run autogen.sh and configure with the correct environment set up (after patching autogen.sh).
start again, cleanup any remnants from the failed autogen.sh runs with './delautogen.sh' or 'make distclean', then 'cd packaging/macosx' and run './osx-build.sh a' and if this succeeds './osx-build.sh c' to configure your source tree.
o.k. - I'm trying to work on that…
I just tried that again with the new 0.47 source package and it ran autogen.sh and configure without errors. (Haven't yet run './osx-build.sh b' to build it).
~suv