aMule Forum
English => Multiplatform => Mac OSX => Topic started by: GodzFire on January 31, 2008, 10:36:48 PM
-
Been awhile since a new WORKING CVS compile was released, (I am using CVS Tues, Oct 2nd).
All the ones since then I have not been able to open.
Would someone be awesome and do a fresh new compile please?
Thanks in advance!
-
Anyone? Please?
-
I'll try to cross-compile one soon, but this will at least take until the end february, because I won't come home (where my PC with the already set-up 10.4 cross-compiler is, I failed getting a cross-compiler for 10.5 to work) earlier.
Would you mind trying to compile one yourself? We'll try to assist you and guide you through the compilation procedure.
-
I built an intel version from CVS. Here is the zip file:
http://badaboum.bidibom.free.fr/aMule.zip
My first impressions are:
- it uses a bit more CPU
- it seems to find more Kad peers.
-
- it uses a bit more CPU
it is debug mode enabled?
I make a mirror:
http://www.mediafire.com/?9dedztobzzo
-
no its not. Should I build one with debug enabled?
-
How about one for PPC? I'm on a PowerBook G4 with 10.5.2 and aMule 2.1.3 and it's sloooooooow! I know nothing about programming or compiling, but am willing to do anything to upgrade to a newer better version.
-
but am willing to do anything to upgrade to a newer better version.
Really? I guess we've found someone who buys Phoenix a Mac after all, so that he can do daily compiles. ;-)
Seriously: Are you afraid of compiling things yourself? I can guide you through a lot of things, but I've never owned a Mac myself, so I don't know everything.
The first step is installing xcode in the most recent version. If you've done that get familiar with macports and install autotools, flex, gettext and libpng.
Well, see the wiki article (http://www.amule.org/wiki/index.php/HowTo_compile_on_Mac) and try to follow the steps for the rest, if there are any problems, please do not hesitate to ask.
kind regards
-
i just tried to compile on an imac (intel) with 10.5.2
making wxmac works but the configure for amule-cvs give me an error:
checking for crypto++ version >= 5.1... configure: error:
Could not find cryptopp header file "cryptlib.h".
Please check if the path "/usr" is valid.
i first also tried a universal build but got
configure:2089: $? = 1
configure:2112: checking for C++ compiler default output file name
configure:2115: g++ -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -bind_at_load conftest.cc >&5
ld: library not found for -lcrt1.10.5.o
collect2: ld returned 1 exit status
ld: library not found for -lcrt1.10.5.o
collect2: ld returned 1 exit status
lipo: can't open input file: /var/folders/It/ItA54lBVE4qvwf3ksxyvPU+++TM/-Tmp-//ccMAg3F5.out (No such file or directory)
configure:2118: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "aMule"
| #define PACKAGE_TARNAME "amule"
| #define PACKAGE_VERSION "SVN"
| #define PACKAGE_STRING "aMule SVN"
| #define PACKAGE_BUGREPORT "admin@amule.org"
| #define PACKAGE "amule"
| #define VERSION "SVN"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2157: error: C++ compiler cannot create executables
-
I have the same problem with a PPC processor and OS X 10.5.1
-
Sorry, this was a change in recent versions which hasn't been updated in the wiki up to reflect this point.
Please download cryptopp from http://www.cryptopp.com and install it on your computer. (You probably have to bundle it, I have unfortunately no experience with this)
It is necessary to execute make -f GNUmakefile instead of just make.
Edit: I don't know about the Universal Binary, maybe someone else does or I'll try to have a look at it once I get near a cross-compiler. (Or someone gives Phoenix a Mac ;) )
-
I downloaded cryptopp and finally I managed to compile aMule!
If someone needs it this is the link http://rapidshare.com/files/91868382/aMule_CVS_20080214.zip.html (http://rapidshare.com/files/91868382/aMule_CVS_20080214.zip.html)
but it's compiled for OSX 10.5 and PPC
I tried to compile a universal binary with the code in the wiki but the result is
$ ./configure --disable-systray --disable-gtk --enable-embedded_crypto
> --with-wx-config=../wxMac-2.8.7/build/wx-config --enable-cas --enable-webserver
> --enable-amulecmd --enable-debug --disable-optimize --disable-dependency-tracking
> CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"
> CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"
checking build system type... powerpc-apple-darwin9.2.0
checking host system type... powerpc-apple-darwin9.2.0
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for g++... g++
checking for C++ compiler default output file name... configure: error: C++ compiler cannot create executables
See `config.log' for more details.
-
Thanks for you package! Could you please attach the file config.log to give us more information about the source of the problem?
-
i can't get the cryptopp to work. i executed make -f GNUmakefile but always get the "can't find cryptlib.h" error. do i have to copy the cryptopp to a special place?
-
Oh, sorry, you need to do a bit more, I failed to mention that.
You have to do either a "make install" (you need root privileges, maybe you have to type "sudo make install" instead) to install it on your computer globably or a "make DESTDIR=/some/path/on/your/mac/ install" to install it to some directory on your Mac and then use --with-crypto-prefix=/some/path/on/your/mac/ as an argument to the configure command when compiling aMule.
-
This is the content of config.log:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by aMule configure SVN, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ ./configure --disable-systray --disable-gtk --enable-embedded_crypto --with-wx-config=../wxMac-2.8.7/build/wx-config --enable-cas --enable-webserver --enable-amulecmd --enable-debug --disable-optimize --disable-dependency-tracking CFLAGS=-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk CXXFLAGS=-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk
## --------- ##
## Platform. ##
## --------- ##
hostname = ***.local
uname -m = Power Macintosh
uname -r = 9.2.0
uname -s = Darwin
uname -v = Darwin Kernel Version 9.2.0: Tue Feb 5 16:15:19 PST 2008; root:xnu-1228.3.13~1/RELEASE_PPC
/usr/bin/uname -p = powerpc
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = Mach kernel version:
Darwin Kernel Version 9.2.0: Tue Feb 5 16:15:19 PST 2008; root:xnu-1228.3.13~1/RELEASE_PPC
Kernel configured for a single processor only.
1 processor is physically available.
1 processor is logically available.
Processor type: ppc7450 (PowerPC 7450)
Processor active: 0
Primary memory available: 1.00 gigabytes
Default processor set: 82 tasks, 282 threads, 1 processors
Load average: 2.87, Mach factor: 0.34
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /opt/local/bin
PATH: /opt/local/sbin
PATH: /usr/bin
PATH: /bin
PATH: /usr/sbin
PATH: /sbin
PATH: /usr/local/bin
PATH: /usr/X11/bin
## ----------- ##
## Core tests. ##
## ----------- ##
configure:1451: checking build system type
configure:1469: result: powerpc-apple-darwin9.2.0
configure:1477: checking host system type
configure:1491: result: powerpc-apple-darwin9.2.0
configure:1513: checking for a BSD-compatible install
configure:1568: result: /usr/bin/install -c
configure:1579: checking whether build environment is sane
configure:1622: result: yes
configure:1687: checking for gawk
configure:1716: result: no
configure:1687: checking for mawk
configure:1716: result: no
configure:1687: checking for nawk
configure:1716: result: no
configure:1687: checking for awk
configure:1703: found /usr/bin/awk
configure:1713: result: awk
configure:1723: checking whether make sets $(MAKE)
configure:1743: result: yes
configure:1915: checking whether to enable maintainer-specific portions of Makefiles
configure:1924: result: no
configure:2031: checking for g++
configure:2047: found /usr/bin/g++
configure:2057: result: g++
configure:2073: checking for C++ compiler version
configure:2076: g++ --version </dev/null >&5
powerpc-apple-darwin9-g++-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465)
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:2079: $? = 0
configure:2081: g++ -v </dev/null >&5
Using built-in specs.
Target: powerpc-apple-darwin9
Configured with: /var/tmp/gcc/gcc-5465~16/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib --build=i686-apple-darwin9 --program-prefix= --host=powerpc-apple-darwin9 --target=powerpc-apple-darwin9
Thread model: posix
gcc version 4.0.1 (Apple Inc. build 5465)
configure:2084: $? = 0
configure:2086: g++ -V </dev/null >&5
g++-4.0: argument to `-V' is missing
configure:2089: $? = 1
configure:2112: checking for C++ compiler default output file name
configure:2115: g++ -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -bind_at_load conftest.cc >&5
ld: library not found for -lcrt1.10.5.o
collect2: ld returned 1 exit status
ld: library not found for -lcrt1.10.5.o
collect2: ld returned 1 exit status
lipo: can't open input file: /var/folders/aT/aTfjKss4HGmISmDJXxYu3k+++TI/-Tmp-//ccUINSOH.out (No such file or directory)
configure:2118: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "aMule"
| #define PACKAGE_TARNAME "amule"
| #define PACKAGE_VERSION "SVN"
| #define PACKAGE_STRING "aMule SVN"
| #define PACKAGE_BUGREPORT "admin@amule.org"
| #define PACKAGE "amule"
| #define VERSION "SVN"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2157: error: C++ compiler cannot create executables
See `config.log' for more details.
## ---------------- ##
## Cache variables. ##
## ---------------- ##
ac_cv_build=powerpc-apple-darwin9.2.0
ac_cv_build_alias=powerpc-apple-darwin9.2.0
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value='-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk'
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=set
ac_cv_env_CXXFLAGS_value='-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk'
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_RC_set=
ac_cv_env_RC_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=powerpc-apple-darwin9.2.0
ac_cv_host_alias=powerpc-apple-darwin9.2.0
ac_cv_path_install='/usr/bin/install -c'
ac_cv_prog_AWK=awk
ac_cv_prog_ac_ct_CXX=g++
ac_cv_prog_make_make_set=yes
## ----------------- ##
## Output variables. ##
## ----------------- ##
ACLOCAL='${SHELL} /Users/simon/source/amule-cvs/missing --run aclocal-1.9'
ALCC_FALSE=''
ALCC_TRUE=''
ALC_FALSE=''
ALC_TRUE=''
ALLOCA=''
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} /Users/simon/source/amule-cvs/missing --run tar'
AMULEWEB_DEFS=''
AMULE_DAEMON_FALSE=''
AMULE_DAEMON_TRUE=''
AMULE_GUI_FALSE=''
AMULE_GUI_TRUE=''
AR=''
AUTOCONF='${SHELL} /Users/simon/source/amule-cvs/missing --run autoconf'
AUTOHEADER='${SHELL} /Users/simon/source/amule-cvs/missing --run autoheader'
AUTOMAKE='${SHELL} /Users/simon/source/amule-cvs/missing --run automake-1.9'
AWK='awk'
BFD_FLAGS=''
BFD_LIB=''
BUILD_CC=''
BUILD_CFLAGS=''
BUILD_CPPFLAGS=''
BUILD_EXEEXT=''
BUILD_INCLUDED_LIBINTL=''
BUILD_LDFLAGS=''
CAS_DEFS=''
CAS_FALSE=''
CAS_TRUE=''
CATOBJEXT=''
CC=''
CCACHE=''
CCDEPMODE=''
CFLAGS='-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -no-cpp-precomp -D_INTL_REDIRECT_MACROS -DNOPCH'
COMPILE_CMD_FALSE=''
COMPILE_CMD_TRUE=''
COMPILE_NLS_FALSE=''
COMPILE_NLS_TRUE=''
CPP=''
CPPFLAGS=''
CRYPTOLIBS=''
CRYPTO_PP_CXXFLAGS=''
CRYPTO_PP_INCLUDE_PREFIX=''
CRYPTO_PP_LDFLAGS=''
CRYPTO_PP_LIB_NAME=''
CRYPTO_PP_PREFIX=''
CRYPTO_PP_STYLE=''
CRYPTO_PP_VERSION_NUMBER=''
CRYPTO_PP_VERSION_STRING=''
CXX='g++'
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS='-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk'
CYGPATH_W='echo'
DATADIRNAME=''
DEFS=''
DEPDIR=''
ECHO_C='ECHO_N=''
ECHO_T=''
ED2K_FALSE=''
ED2K_TRUE=''
EGREP=''
ENABLE_IP2COUNTRY_FALSE=''
ENABLE_IP2COUNTRY_TRUE=''
ENABLE_UPNP_FALSE=''
ENABLE_UPNP_TRUE=''
EXEEXT=''
EXEEXT=''
GDLIB_CFLAGS=''
GDLIB_CFLAGS_ONLY=''
GDLIB_CONFIG_PATH=''
GDLIB_CPPFLAGS=''
GDLIB_CXXFLAGS=''
GDLIB_CXXFLAGS_ONLY=''
GDLIB_LDFLAGS=''
GDLIB_LIBS=''
GDLIB_LIBS_STATIC=''
GDLIB_VERSION=''
GENCAT=''
GENERATE_FLEX_HEADER_FALSE=''
GENERATE_FLEX_HEADER_TRUE=''
GEOIP_INCLUDE=''
GEOIP_LIB=''
GLIBC21=''
GMSGFMT=''
HAVE_FLEX_EXTENDED=''
HAVE_GETTEXT=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
INSTOBJEXT=''
INTLBISON=''
INTLLIBS=''
INTLOBJS=''
INTL_LIBTOOL_SUFFIX_PREFIX=''
LD=''
LDFLAGS=' -bind_at_load'
LEX=''
LEXLIB=''
LEX_OUTPUT_ROOT=''
LIBICONV=''
LIBINTL=''
LIBOBJS=''
LIBPNG_CFLAGS=''
LIBPNG_CONFIG_PATH=''
LIBPNG_CXXFLAGS=''
LIBPNG_LDFLAGS=''
LIBPNG_LIBS=''
LIBS=''
LTLIBICONV=''
LTLIBINTL=''
LTLIBOBJS=''
MAINT='#'
MAINTAINER_MODE_FALSE=''
MAINTAINER_MODE_TRUE='#'
MAKEINFO='${SHELL} /Users/simon/source/amule-cvs/missing --run makeinfo'
MKINSTALLDIRS=''
MONOLITHIC_FALSE=''
MONOLITHIC_TRUE=''
MSGFMT=''
MSGMERGE=''
NEED_CORESERVICES_FALSE=''
NEED_CORESERVICES_TRUE=''
NEED_RC_FALSE=''
NEED_RC_TRUE=''
OBJEXT=''
PACKAGE='amule'
PACKAGE_BUGREPORT='admin@amule.org'
PACKAGE_NAME='aMule'
PACKAGE_STRING='aMule SVN'
PACKAGE_TARNAME='amule'
PACKAGE_VERSION='SVN'
PATH_SEPARATOR=':'
POSUB=''
POW_LIB=''
RANLIB=''
RC=''
RCFLAGS=''
READLINE_LIBS=''
RESOLV_LIB=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
SVNDATE=''
SYS_WIN32_FALSE=''
SYS_WIN32_TRUE=''
USE_INCLUDED_LIBINTL=''
USE_NLS=''
VERSION='SVN'
WEB_FALSE=''
WEB_TRUE=''
WXBASE_CFLAGS=''
WXBASE_CXXFLAGS=''
WXBASE_LIBS=''
WXCAS_FALSE=''
WXCAS_TRUE=''
WX_CFLAGS=''
WX_CFLAGS_ONLY=''
WX_CONFIG_PATH=''
WX_CPPFLAGS=''
WX_CXXFLAGS=''
WX_CXXFLAGS_ONLY=''
WX_DEBUG=''
WX_LIBS=''
WX_LIBS_STATIC=''
WX_PORT=''
WX_RESCOMP=''
WX_SHARED=''
WX_UNICODE=''
WX_VERSION_FULL=''
WX_VERSION_MAJOR=''
WX_VERSION_MINOR=''
X11LIBS=''
XGETTEXT=''
YACC=''
ac_ct_AR=''
ac_ct_BUILD_CC=''
ac_ct_CC=''
ac_ct_CXX='g++'
ac_ct_LD=''
ac_ct_RANLIB=''
ac_ct_RC=''
ac_ct_STRIP=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__fastdepCXX_FALSE=''
am__fastdepCXX_TRUE=''
am__include=''
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build='powerpc-apple-darwin9.2.0'
build_alias=''
build_cpu='powerpc'
build_os='darwin9.2.0'
build_vendor='apple'
ccache=''
ccache_prefix=''
datadir='${prefix}/share'
docdir=''
exec_prefix='NONE'
host='powerpc-apple-darwin9.2.0'
host_alias=''
host_cpu='powerpc'
host_os='darwin9.2.0'
host_vendor='apple'
includedir='${prefix}/include'
infodir='${prefix}/info'
install_sh='/Users/simon/source/amule-cvs/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='${prefix}/var'
mandir='${prefix}/man'
mkdir_p='$(mkinstalldirs)'
oldincludedir='/usr/include'
prefix='NONE'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''
## ----------- ##
## confdefs.h. ##
## ----------- ##
#define PACKAGE "amule"
#define PACKAGE_BUGREPORT "admin@amule.org"
#define PACKAGE_NAME "aMule"
#define PACKAGE_STRING "aMule SVN"
#define PACKAGE_TARNAME "amule"
#define PACKAGE_VERSION "SVN"
#define VERSION "SVN"
configure: exit 77
-
I built an intel version from CVS. Here is the zip file:
http://badaboum.bidibom.free.fr/aMule.zip
My first impressions are:
- it uses a bit more CPU
- it seems to find more Kad peers.
Nice try Matthis, unfortunately as soon as I double click to run it, it closes :-/
-
I downloaded cryptopp and finally I managed to compile aMule!
If someone needs it this is the link http://rapidshare.com/files/91868382/aMule_CVS_20080214.zip.html (http://rapidshare.com/files/91868382/aMule_CVS_20080214.zip.html)
but it's compiled for OSX 10.5 and PPC
I tried to compile a universal binary with the code in the wiki but the result is
$ ./configure --disable-systray --disable-gtk --enable-embedded_crypto
> --with-wx-config=../wxMac-2.8.7/build/wx-config --enable-cas --enable-webserver
> --enable-amulecmd --enable-debug --disable-optimize --disable-dependency-tracking
> CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"
> CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"
checking build system type... powerpc-apple-darwin9.2.0
checking host system type... powerpc-apple-darwin9.2.0
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for g++... g++
checking for C++ compiler default output file name... configure: error: C++ compiler cannot create executables
See `config.log' for more details.
Any chance you could compile for 10.4 and above?
-
Any chance you could compile for 10.4 and above?
Yes but it takes time because I have to recompile wxMac on another machine with 10.4 on it.
Is there anybody who knows how to compile aMule on Leopard so that it's runnable on Tiger too?
-
Hi everybody,
I had started a topic here ( http://forum.amule.org/index.php?topic=14353.0 ) but wuischke was kind enough to direct me to this topic. :)
Anyway, I have a running Debian file server with amuled, and I need to control it remotely from two network Macs (one PPC running OS X 10.3.9, and one Intel running OS X 10.4.11).
So I'm desperately seeking for amulegui binaries for both Mac versions (amulegui, not amule). Could someone please provide this ? ;)
Optionally I could try to use amuleweb, but the last time I tried, I remember a really bad-looking interface (sorry, but it had absolutely nothing to do with the official eMule web interface for example). So if the amuleweb interface has REALLY changed, could someone indicate me where I can download it ?
Thanks in advance for your help & Best regards,
Jose
-
Edit: I don't know about the Universal Binary, maybe someone else does or I'll try to have a look at it once I get near a cross-compiler. (Or someone gives Phoenix a Mac ;) )
That is the only possible solution for this problem :P
-
ok, it took some time but here it is, amule cvs 20080218: http://www.sendspace.com/file/hqiibe
to configure i used:
./configure --disable-systray --disable-gtk --enable-embedded_crypto
--with-wx-config=../wxMac-2.8.7/build/wx-config --enable-cas --enable-amulecmd
--enable-debug --disable-optimize --enable-wxcas --disable-nls --enable-webserver --enable-amule-gui
i tried to enable the amule-gui but i can't find it in the resulting app. but the included webserver seems to work.
-
Thanks bongo.
Now can someone tell us why amulegui doesn't seem to be in the resulting app, as bongo says ? ???
Thank you.
EDIT : bongo, your release doesn't work on my PPC Mac under OS X 10.3.9. The error message says : "You can't open the application 'aMule' because it's either damaged or incomplete".
-
doesn't work on my PPC Mac under OS X 10.3.9. The error message says : "You can't open the application 'aMule' because it's either damaged or incomplete".
it can't because it's no universal binary. just for intel. i also tried a universal binary but had similar problems as scalimani.
-
I've found this release for PPC ( http://forum.amule.org/index.php?topic=14197.0 ). I've downloaded it, and in order to make it work I've tried lots of things. Although I'm a terminal newbie, I've managed to install MacPorts, then installed libpng (which required Xcode 1.5 in order to use the 'make' command - 350 MB download, thank you), then installed libiconv, then... it still doesn't work and I really feel that I won't go any further.
I don't think any Mac OS X user is expected to do all that in order to make an app like aMule work, so I quit. >:( >:(
Right now I'm just expecting a *working* amulegui version, with no complicated operations (double-click on the app, that's all - we're talking OS X here, not command-line UNIX !). Is that too much to ask for in 2008 guys ?... :-[
This is totally crazy !!! :o
-
Jose, there is NO developer with access to a Mac. We just cannot create double-click-the-app packages for you, because we don't have the means to do so.
We have to rely on users to do the testing and on creating the packages. You see, universal binary compilation is broken and this is the only major point delaying the release of aMule 2.2.0 right now.
I mean, we are talking about open source here. All the developers are doing the work in their free time without getting paid. BUT: We are bribable. Buy Phoenix a Mac and he'll do daily builds for Mac OS X and we'll make him responsible for every problem related to the Mac port of aMule.
The cheapest prices I found were R$ 1600 (about 5% more expensive than here in Germany) for a Mac Mini, so it's not something you buy just to get your hobby software project perfectly working on a system you don't own yourself.
---
Technically speaking it is possible to cross-compile for Mac. But setting up a cross-compiler is very hard and time consuming (I did this at home on a i686 machine, when I tried it again on my x86_64 notebook, I failed) and there's still the problem of testing.
-
I am trying to install Leopard 10.5 on my computer to try to pack aMule.
No promises in a short time... I will see that I do... :-\
-
if all goes well is there more needed to get amule-gui then the --enable-amule-gui in the configure? perhaps i just ignored some hint and so it didn't get built.
<rant mode on>
I don't think any Mac OS X user is expected to do all that in order to make an app like aMule work, so I quit. Right now I'm just expecting a *working* amulegui version
hmm, perhaps you really better quit and find your luck elsewhere. i'm also a mac user but i expect nothing from an open source project. i'm happy if there is software i can use and if there are some flaws i try my best to help to fix or i live with them.
there is a working amule for mac os x, in fact there are different versions, universal, intel, ppc. not all are the latest and greatest and probably some functions need some work. so what? did you paid a lot of money? you can pay a bunch for ms office and get crap anyways. here you have to pay nothing but get a lot of functionality and helping hands.
<rant mode off>
sorry. ::)
-
Jose, there is NO developer with access to a Mac.
Yes, I know that, unfortunately, and I understand. But what about the experienced users ? Isn't there a single user out there who knows how to compile everything correctly ? (I mean "without errors", "without need for the final user to download additional libraries", etc... just double-click, like every Mac app should work).
I mean : if there are REALLY some working Mac versions, like bongo is pretending, then why don't you simply put the links on your home page / downloads section ? Now that would be really cool ! 8)
In fact what amazes me is that there isn't a single link pointing to any working Mac binary on your home page. Why is that ? ???
My best guess is that currently there ISN'T any really working Mac version (I mean "guaranteed, working on most Macs without hassle"). But don't take me wrong : I understand that this is open source and there is no guarantee. I'm used to open source, so no problem about that. When I wrote "expecting" I should have written "hoping". ;)
I am trying to install Leopard 10.5 on my computer to try to pack aMule.
No promises in a short time... I will see that I do... :-\
Yes,, there's now possible to install quite easily Mac OS X (10.3, 10.4 or 10.5) on a PC. I'm sure for a developer it would be no trouble doing it. Thank you. :)
-
i use a working mac version. for some days a self compiled one, before it was another cvs version i found here in the forum. even before with 10.4 i used the version from http://forum.amule.org/index.php?topic=5051.0 and before that i just used the "old" from http://www.amule.org/
all of them worked for me. i never had to compile it for myself, i just tried it out of curiosity and to see if i get it done. thanks to a lot of helping hints it was no big problem.
but i just use the normal app and amule-cmd the remote control the speed settings from a daemon.
so what is you exact problem? is it the missing amule-gui or don't you find a version from amule which starts on your mac?
regarding amule-gui perhaps we get some enlightment why it isn't compiled even with the enable-amule-gui. or perhaps it is? is amule-gui a separate app like amule-cmd? or is this just the normal gui you get when you start the amule package on a mac?
-
Is there a amulegui binary in the amule-cvs/src folder after compilation? Macs uses these weird packages, so maybe it is not included in this package.
-
you are right. :)
in the mac_packager util all compiled tools are copied to the package but amulegui isn't:
echo -n "Step 2: Copying aMule to app bundle... "
cp src/amule aMule.app/Contents/MacOS/
cp src/webserver/src/amuleweb aMule.app/Contents/MacOS/
cp src/ed2k aMule.app/Contents/MacOS/
cp src/amulecmd aMule.app/Contents/MacOS/
cp -R src/webserver aMule.app/Contents/Resources
so what's missing here is a cp src/amulegui aMule.app/Contents/MacOS/but this wouldn't be enough because then there would be 2 apps in the package and a doubleclick would open just amule is always. so perhaps we need a separate package created just for amulegui.
so what i did is a bit of a dirty hack. i copied the already compiled amulegui to the package manually and renamed it to amule so it is started when you doubleclick the package. i tested it on my intel imac and can connect to the also running standard amule (so connecting to localhost)
i uploaded it to http://www.sendspace.com/file/t9zzb2
but it'sonly for intel, so perhaps someone can do this also for ppc.
-
Could you please fill a bug report about this? Hopefully someone with a better understanding of Mac packages can create a second package for creating an amuleweb package as well.
-
i filed it under http://bugs.amule.org/view.php?id=1268
thanks a lot for your help
i include now also a modified mac_packager and a amuleGui.app template with the bung report. not sure if the packager copies all or perhaps to much to the amuleGui package but at least i got a working amuleGui with it. so perhaps this is soome help for anybody who makes a built for ppc
-
Ok Guy, i am an "experienced MAC user", i compiled some time ago an old version of amulegui from CVS. November 20 2007. It's only for PPC, 10.4. I can share, but you will need a SAME CVS DATE amuled, because of problem related on protocol used by the GUI and server to talk. (TO DEV: Is this right?)
BUT, recently i try to build tha lastest CVS but it fail to build. Makefile error i guess. I had a LOT of dupicated declaration of wxString operator error.
My proposal is: I can help you to make a FULL amule.app and a simple amulegui.app the (process is simple, and the difference is null :P), BUT i need to know the lastest CVS wich can be succesfully compile.
I will make a universal binary but I read earlier that does not work.
I advise you i haven't much time, and i will do this after the dinner, so don't expect result in a few time. By the way i can promise i will make my best effort!
-
i include now also a modified mac_packager and a amuleGui.app template with the bung report. not sure if the packager copies all or perhaps to much to the amuleGui package but at least i got a working amuleGui with it. so perhaps this is soome help for anybody who makes a built for ppc
Regarding the creation of amulegui.app for mac, the step to do is very simple.
Proceed as normal, by enable amulegui in "configure", compile and after all is finish, do in sequence:
1 - BEFORE run mac_package,make a copy of aMule.app, so suo will have aMule.app and "aMule copy.app"
2 - run mac_package, this will make a FULL aMule app.
3 - Now move the aMule.app to another place, outside the amule compilation dir, and rename "aMule copy.app" to aMule.app
4 - delete the file src/amule and rename the src/amulegui file in amule
5 - rerun mac_package
6 - now in the "new" aMule.app, you will have the amulegui ONLY. So you can rename the aMule.app in somthing you think is better.
-----
Alternatively to this procedure is to make another "aMule RemoteGUI.app" skeleton (by copy and rename the aMule.app"), change the manifest of this one, and change the mac_package script. I tink this will be the best option for aMule devs.
EDIT:
The files thath need to be changed is Info.plist, at key: CFBundleExecutable, replace the string "amule" with "amulegui".
-------
EDIT:
This is my version of the GUI, only for PPC 10.4 CVS 20071120. Quite old, but just let me know if it show you the login maks. If you see the maks all is ok, but it is possible that you can can control the remote server. But this is porblem related to the age of of may build, and because the code is changed meanwile.
http://www.albazzano.it/aMule-GUI.zip
-
blackfede, can you please post your build errors with today's tarball?
-
blackfede, can you please post your build errors with today's tarball?
Sure, but investigatin it more, i think it could be a problem of "extern C" somewere... Ah, this is the 20080223 tarball!
By the way, here is the configure:
./configure --enable-amule-gui --disable-debug --disable-amule-daemon --disable-amulecmd --disable-webserver --disable-cas --disable-wxcas --disable-systray --disable-gtk --with-crypto-prefix=../../.libcryptopp552/installation/
Configure script has finished system check.
Configured aMule SVN for 'powerpc-apple-darwin8.11.0'.
aMule enabled options:
**** aMule Core ****
Prefix where aMule should be installed? /usr/local
Should aMule be compiled with i18n support? yes
Should aMule be compiled in debug mode? no
Should aMule be compiled with profiling? no
Should aMule be compiled with optimizations? no
Should aMule be compiled with UPnP support? yes
Should aMule be compiled with IP2country support? no
Should aMule monolithic application be built? yes
Should aMule daemon version be built? no
Should aMule remote gui be built? (EXPERIMENTAL) yes
Crypto++ library/headers style? installed
**** aMule TextClient ****
Should aMule Command Line Client be built? no
**** aMule WebServer ****
Should aMule WebServer be built? no
**** aMule ED2K Links Handler ****
Should aMule ED2K Links Handler be built? yes
**** aMuleLinkCreator ****
Should aMuleLinkCreator GUI version (alc) be built? no
Should aMuleLinkCreator for console (alcc) be built? no
**** aMule Statistics ****
Should C aMule Statistics (CAS) be built? no
Should aMule GUI Statistics (wxCas) be built? no
**** General Libraries and Tools ****
Should ccache support be enabled? no
Libraries aMule will use to build:
wxWidgets 2.8.7 (mac,shared)
crypto++ 5.5.2 (installed)
zlib 1.2.3
And here the error:
if g++ -DHAVE_CONFIG_H -I. -I. -I../../../.. -isystem /opt/local/lib/wx/include/mac-unicode-release-2.8 -isystem /opt/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXMAC__ -I../../../../src -I../../../../src/libs -I../../../../src/include -isystem ../../.libcryptopp552/installation//include -D__CRYPTO_INSTALLED__ -D__WEAK_CRYPTO__ -W -Wall -Wshadow -Wundef -DUSE_WX_EXTENSIONS -MT libec_a-ECTag.o -MD -MP -MF ".deps/libec_a-ECTag.Tpo" -c -o libec_a-ECTag.o `test -f 'ECTag.cpp' || echo './'`ECTag.cpp; \
then mv -f ".deps/libec_a-ECTag.Tpo" ".deps/libec_a-ECTag.Po"; else rm -f ".deps/libec_a-ECTag.Tpo"; exit 1; fi
/opt/local/include/wx-2.8/wx/defs.h:603: error: template with C linkage
/opt/local/include/wx-2.8/wx/string.h:1048: error: declaration of C function 'wxString operator+(const wxString&, wxChar)' conflicts with
/opt/local/include/wx-2.8/wx/string.h:1046: error: previous declaration 'wxString operator+(const wxString&, const wxString&)' here
/opt/local/include/wx-2.8/wx/string.h:1050: error: declaration of C function 'wxString operator+(wxChar, const wxString&)' conflicts with
/opt/local/include/wx-2.8/wx/string.h:1048: error: previous declaration 'wxString operator+(const wxString&, wxChar)' here
/opt/local/include/wx-2.8/wx/string.h:1053: error: declaration of C function 'wxString operator+(const wxString&, const wxChar*)' conflicts with
/opt/local/include/wx-2.8/wx/string.h:1050: error: previous declaration 'wxString operator+(wxChar, const wxString&)' here
/opt/local/include/wx-2.8/wx/string.h:1056: error: declaration of C function 'wxString operator+(const wxChar*, const wxString&)' conflicts with
/opt/local/include/wx-2.8/wx/string.h:1053: error: previous declaration 'wxString operator+(const wxString&, const wxChar*)' here
/opt/local/include/wx-2.8/wx/string.h:1421: error: declaration of C function 'wxString operator+(const wxString&, const wxString&)' conflicts with
/opt/local/include/wx-2.8/wx/string.h:1056: error: previous declaration 'wxString operator+(const wxChar*, const wxString&)' here
/opt/local/include/wx-2.8/wx/string.h:1422: error: declaration of C function 'wxString operator+(const wxString&, wxChar)' conflicts with
/opt/local/include/wx-2.8/wx/string.h:1421: error: previous declaration 'wxString operator+(const wxString&, const wxString&)' here
/opt/local/include/wx-2.8/wx/string.h:1423: error: declaration of C function 'wxString operator+(wxChar, const wxString&)' conflicts with
/opt/local/include/wx-2.8/wx/string.h:1422: error: previous declaration 'wxString operator+(const wxString&, wxChar)' here
......
......
(lot of message about duplicated declaration of operator==, operator!=, ecc)
../../../../src/libs/common/MuleDebug.h: In constructor 'CMuleException::CMuleException(const wxString&, const wxString&)':
../../../../src/libs/common/MuleDebug.h:59: error: no match for 'operator+' in 'type + "\000\000\000:\000\000\000 \000\000\000"'
/opt/local/include/wx-2.8/wx/string.h:1620: note: candidates are: wxString operator+(const wxWCharBuffer&, const wxString&)
make[7]: *** [libec_a-ECTag.o] Error 1
make[6]: *** [all] Error 2
make[5]: *** [all-recursive] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
-
Alternatively to this procedure is to make another "aMule RemoteGUI.app" skeleton (by copy and rename the aMule.app"), change the manifest of this one, and change the mac_package script. I tink this will be the best option for aMule devs.
as i said i attached a amulegui template (or skeleton as you said )to the bug report together with a try for a modified packager which worked for me. to make it easier for those not wanting to register with the bugtracker here it is again: http://www.sendspace.com/file/t0e18j
the amulegui template already has the modified plist so you can copy the compiled amulegui from /src into the package without renaming.
i had no problems compiling the 20080218 tarball. did you compiled wxmac for the same platform (ppc) as amule? i had similar problems trying to compile a universal binary. i had configured wxmac for universal and amule universal failed, but then also the intel built failed. after a new configure and make of wxmac just for intel the amule mac also went through.
-
Yes i see you bugreport, i have only witten the step, so if someone want to repeat it, it's possible. ;D
I was afraid of my wx installation, but i tried to compile the example present in the source of wx and all works fine! This is strange! By the way, i installed wxWindows 2.8 using macport. Did you install all from sources of using macport?
-
i downloaded and built wxmac as described in the wiki. i just installed the 4 packages mentioned in the wiki with macport. after having problems with cryptopp i wanted to install it with macport but this was no solution. so i also installed cryptopp from the sources, which is also described in the wiki and wuischke mentioned also in this thread a bit above.
-
Yes, i also buil crypto++ myself, the one in macport is too old. Now i have compiled wxmac by myself, but i have th same problem... this is SO frustrating! I will try to download an old snapshot and seed what it came out...
-
the same problem? perhaps amule tries to link to the same old built instead of the new one? is the prefix correct?
i just followed wuischke's hints from http://forum.amule.org/index.php?topic=14342.msg76238#msg76238 and http://forum.amule.org/index.php?topic=14342.msg76266#msg76266
i think i also did a make clean after the univerasl binary tries but i don't know if this matters.
-
Thanks for the hints, but my is a problem related to compile of amule, not cpypto++. After investigatin more i discovered the config is ignoring my --with-wxpath directive and still take the old wxversion. I have now make a full cleanof and now i'am waiting the building of wx. Hope this will solve!
-
--with-wxdir=PATH Use uninstalled version of wxWidgets in PATH
-
Sure, i have used that. I've made a mistake in my previous post, sorry.
So, reassuming: now i make a full cleanup of my wx installation (remains only 2.5, but is installed by macos, and i can't remove this). Compiled the last version of wx, following exactly the istruction on wiki, and get:
$> ./wx-config --list
Default config is mac-unicode-debug-static-2.8
Default config will be used for output
And this is ok. I've tryed to compile a old CVS version of November 2007, only to check the goodness of my wx installation. And all is fine. (i didn't let the compilation finish but after a while without error i'm almost sure that all is fine). I also compiled and executed some of the example present in wx source distribution.
At this point i started the compilation of amule CVS 20080218, ( i chose this because bongo reported to compile succesful) but this will fail almost for the same reason ("template with C linkage").
So i dowload the 20080226, but also this hang with the same error.
Now the question is: if an old amule version is compiling, if the sample is compiling is it possible that my problem is related to wx? I don't think so.
@Bongo, please can you check the CVS date of your build?
-
blackfede, can you check in which tarball the error introduced? At least if it's still available from the download page...
-
i checked my version and it is cvs 20080218. i will try another cvs date in the evening just to see if this makes a difference. here http://forum.amule.org/index.php?topic=14197.0 is a report of a succesful ppc built from the cvs 20080107 but you know this because you also posted there. did you try to unistall the macport version of wxmac?
-
@Bongo: previusly,when i post the first message on this thread i had wx from macport. That version works fine with Nov. 2007 version. In fact i build an amule-gui version for mysefl.
Now i build by hand the wx version dowloaded from wx site, and have ONLY this version.
@ GonoszTopi:
Sure i will try starting with the oldest CVS tarball and post here the result as soon as i get something!
-
I really don't understand. ??? It's possible that bongo can compile the 20080218 version and i can't?
I mean, my wx installation and build is clean: wx 2.8 mac unicode debug; the sample program in wx source tarbal compile and execute fine; my old amule snapshot 20071120 is compilig fine with the same wx installation that fail with 20080218.
Is it possible the problem is in amule code? Once we found a person who say it can compile, doesn't this prove the sanity of amule code?
I'm writing this because i don't want to make a bug hunt, if there is no bug and is a problem of mine!! :(
So returning to the request of GonoszTopi: i had downloaded the 20080125 but this fail to. I'm so sorry abut this... :-[
-
perhaps it's some problem with ppc? i tried it now with todays tarball aMule-CVS-20080226.tar.bz2.
for configure i used ./configure --disable-systray --disable-gtk --enable-embedded_crypto --with-wx-config=../wxMac-2.8.7/build/wx-config --enable-cas --enable-amulecmd --enable-debug --disable-optimize --enable-wxcas --disable-nls --enable-webserver --enable-amule-gui and got Configure script has finished system check.
Configured aMule SVN for 'i686-apple-darwin9.2.0'.
aMule enabled options:
**** aMule Core ****
Prefix where aMule should be installed? /usr/local
Should aMule be compiled with i18n support? no
Should aMule be compiled in debug mode? yes
Should aMule be compiled with profiling? no
Should aMule be compiled with optimizations? no
Should aMule be compiled with UPnP support? yes
Should aMule be compiled with IP2country support? no
Should aMule monolithic application be built? yes
Should aMule daemon version be built? no
Should aMule remote gui be built? (EXPERIMENTAL) yes
Crypto++ library/headers style? installed
**** aMule TextClient ****
Should aMule Command Line Client be built? yes
**** aMule WebServer ****
Should aMule WebServer be built? yes
**** aMule ED2K Links Handler ****
Should aMule ED2K Links Handler be built? yes
**** aMuleLinkCreator ****
Should aMuleLinkCreator GUI version (alc) be built? no
Should aMuleLinkCreator for console (alcc) be built? no
**** aMule Statistics ****
Should C aMule Statistics (CAS) be built? yes
Should aMule GUI Statistics (wxCas) be built? yes
**** General Libraries and Tools ****
Should ccache support be enabled? no
Libraries aMule will use to build:
wxWidgets 2.8.7 (mac,static)
crypto++ 5.5.2 (installed)
libpng 1.2.23
libgd 2.0.35
zlib 1.2.3
then the make was successful and after calling the mac_packager i got a working amule. on difference seems to be that you get a wxwidgets shared after configure and i get a static at least when i compare to your posted configure result a bit above.
-
Well i try to recompile wx statical, and cross my finger! :P
EDIT: Bongo, how did you get a statically linked wx lib? I don't see any config option to set this.
-
i did nothing special to make it static. i just followed the wiki after downloading and expanding wxmac into the same folder as amule.
-
I compiled it just fine on PPC and Leopard with the 26th Feb SVN version.
It complained about not having BFD, but it didn't matter. I did not compile a debug version though.
-
I have compiled the Wx libs and make them static, according to wx-config utput.
I've relaunch the compilation of aMule, but the error, the same, is still here.
Maybe is really a problem with Tiger PPC. But i should not understand why!
I can give a try compiling a Genuary, 2008 snapshot if some Devs can post here a tarball, just to see if that version will compile fine.
@Eisa01:
Here http://forum.amule.org/index.php?topic=14486.0 it's discussing about "bfd.h". The message is still there even in the case you have binutils installed.
-
blackfede: Here's January 19th: http://www.htw-dresden.de/~s59596/
-
configure script is missign here, is it sufficient, after extraction, run the autogen.sh script?
-
Yes, it is even necessary to run it. ;) We developers have to do it every time we compile from a check-out, too.
-
This couldn't be true! :o I'm surely cursed! :-\ This one fail too. But the error reported is a bit different in the final part. Here is a cut&paste.
Making all in ec
make all-recursive
Making all in cpp
make all-am
g++ -DHAVE_CONFIG_H -I. -I../../../.. -isystem /Users/blackfede/.wxMac-287-ppc//lib/wx/include/mac-unicode-debug-static-2.8 -isystem /Users/blackfede/.wxMac-287-ppc//include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXDEBUG__ -D__WXMAC__ -I../../../../src -I../../../../src/libs -I../../../../src/include -isystem ../../.libcryptopp552/installation//include -D__CRYPTO_INSTALLED__ -g -D__DEBUG__ -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC -W -Wall -Wshadow -Wundef -ggdb -fno-inline -fmessage-length=0 -DUSE_WX_EXTENSIONS -MT libec_a-ECTag.o -MD -MP -MF .deps/libec_a-ECTag.Tpo -c -o libec_a-ECTag.o `test -f 'ECTag.cpp' || echo './'`ECTag.cpp
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/defs.h:603: error: template with C linkage
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1048: error: declaration of C function 'wxString operator+(const wxString&, wxChar)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1046: error: previous declaration 'wxString operator+(const wxString&, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1050: error: declaration of C function 'wxString operator+(wxChar, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1048: error: previous declaration 'wxString operator+(const wxString&, wxChar)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1053: error: declaration of C function 'wxString operator+(const wxString&, const wxChar*)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1050: error: previous declaration 'wxString operator+(wxChar, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1056: error: declaration of C function 'wxString operator+(const wxChar*, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1053: error: previous declaration 'wxString operator+(const wxString&, const wxChar*)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1421: error: declaration of C function 'wxString operator+(const wxString&, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1056: error: previous declaration 'wxString operator+(const wxChar*, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1422: error: declaration of C function 'wxString operator+(const wxString&, wxChar)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1421: error: previous declaration 'wxString operator+(const wxString&, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1423: error: declaration of C function 'wxString operator+(wxChar, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1422: error: previous declaration 'wxString operator+(const wxString&, wxChar)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1424: error: declaration of C function 'wxString operator+(const wxString&, const wxChar*)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1423: error: previous declaration 'wxString operator+(wxChar, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1425: error: declaration of C function 'wxString operator+(const wxChar*, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1424: error: previous declaration 'wxString operator+(const wxString&, const wxChar*)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator==(const wxString&, const wxChar*)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1562: error: declaration of C function 'bool operator==(const wxString&, const wxChar*)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1560: error: previous declaration 'bool operator==(const wxString&, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator==(const wxChar*, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1564: error: declaration of C function 'bool operator==(const wxChar*, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1562: error: previous declaration 'bool operator==(const wxString&, const wxChar*)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator!=(const wxString&, const wxChar*)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1568: error: declaration of C function 'bool operator!=(const wxString&, const wxChar*)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1566: error: previous declaration 'bool operator!=(const wxString&, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator!=(const wxChar*, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1570: error: declaration of C function 'bool operator!=(const wxChar*, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1568: error: previous declaration 'bool operator!=(const wxString&, const wxChar*)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator<(const wxString&, const wxChar*)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1574: error: declaration of C function 'bool operator<(const wxString&, const wxChar*)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1572: error: previous declaration 'bool operator<(const wxString&, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator<(const wxChar*, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1576: error: declaration of C function 'bool operator<(const wxChar*, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1574: error: previous declaration 'bool operator<(const wxString&, const wxChar*)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator>(const wxString&, const wxChar*)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1580: error: declaration of C function 'bool operator>(const wxString&, const wxChar*)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1578: error: previous declaration 'bool operator>(const wxString&, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator>(const wxChar*, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1582: error: declaration of C function 'bool operator>(const wxChar*, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1580: error: previous declaration 'bool operator>(const wxString&, const wxChar*)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator<=(const wxString&, const wxChar*)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1586: error: declaration of C function 'bool operator<=(const wxString&, const wxChar*)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1584: error: previous declaration 'bool operator<=(const wxString&, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator<=(const wxChar*, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1588: error: declaration of C function 'bool operator<=(const wxChar*, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1586: error: previous declaration 'bool operator<=(const wxString&, const wxChar*)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator>=(const wxString&, const wxChar*)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1592: error: declaration of C function 'bool operator>=(const wxString&, const wxChar*)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1590: error: previous declaration 'bool operator>=(const wxString&, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator>=(const wxChar*, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1594: error: declaration of C function 'bool operator>=(const wxChar*, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1592: error: previous declaration 'bool operator>=(const wxString&, const wxChar*)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator==(const wxString&, const wxWCharBuffer&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1598: error: declaration of C function 'bool operator==(const wxString&, const wxWCharBuffer&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1564: error: previous declaration 'bool operator==(const wxChar*, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator==(const wxWCharBuffer&, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1600: error: declaration of C function 'bool operator==(const wxWCharBuffer&, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1598: error: previous declaration 'bool operator==(const wxString&, const wxWCharBuffer&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator!=(const wxString&, const wxWCharBuffer&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1602: error: declaration of C function 'bool operator!=(const wxString&, const wxWCharBuffer&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1570: error: previous declaration 'bool operator!=(const wxChar*, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator!=(const wxWCharBuffer&, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1604: error: declaration of C function 'bool operator!=(const wxWCharBuffer&, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1602: error: previous declaration 'bool operator!=(const wxString&, const wxWCharBuffer&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'wxString operator+(const wxString&, const wxWCharBuffer&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1618: error: declaration of C function 'wxString operator+(const wxString&, const wxWCharBuffer&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1425: error: previous declaration 'wxString operator+(const wxChar*, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'wxString operator+(const wxWCharBuffer&, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1620: error: declaration of C function 'wxString operator+(const wxWCharBuffer&, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1618: error: previous declaration 'wxString operator+(const wxString&, const wxWCharBuffer&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator==(wxChar, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1633: error: declaration of C function 'bool operator==(wxChar, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1600: error: previous declaration 'bool operator==(const wxWCharBuffer&, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator==(const wxString&, wxChar)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1634: error: declaration of C function 'bool operator==(const wxString&, wxChar)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1633: error: previous declaration 'bool operator==(wxChar, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator!=(wxChar, const wxString&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1635: error: declaration of C function 'bool operator!=(wxChar, const wxString&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1604: error: previous declaration 'bool operator!=(const wxWCharBuffer&, const wxString&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h: In function 'bool operator!=(const wxString&, wxChar)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1636: error: declaration of C function 'bool operator!=(const wxString&, wxChar)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/string.h:1635: error: previous declaration 'bool operator!=(wxChar, const wxString&)' here
--- CUT ---
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h: In function 'wxULongLong operator+(long unsigned int, const wxULongLong&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1060: error: declaration of C function 'wxULongLong operator+(long unsigned int, const wxULongLong&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1047: error: previous declaration 'wxLongLong operator+(long int, const wxLongLong&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h: In function 'wxLongLong operator-(long unsigned int, const wxULongLong&)':
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1062: error: declaration of C function 'wxLongLong operator-(long unsigned int, const wxULongLong&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1048: error: previous declaration 'wxLongLong operator-(long int, const wxLongLong&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h: At global scope:
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1070: error: declaration of C function 'wxTextOutputStream& operator<<(wxTextOutputStream&, long long unsigned int)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:557: error: previous declaration 'wxTextOutputStream& operator<<(wxTextOutputStream&, const wxULongLongNative&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1071: error: declaration of C function 'wxTextOutputStream& operator<<(wxTextOutputStream&, long long int)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1070: error: previous declaration 'wxTextOutputStream& operator<<(wxTextOutputStream&, long long unsigned int)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1073: error: declaration of C function 'wxTextInputStream& operator>>(wxTextInputStream&, long long unsigned int&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:559: error: previous declaration 'wxTextInputStream& operator>>(wxTextInputStream&, wxULongLongNative&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1074: error: declaration of C function 'wxTextInputStream& operator>>(wxTextInputStream&, long long int&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1073: error: previous declaration 'wxTextInputStream& operator>>(wxTextInputStream&, long long unsigned int&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/dynarray.h:993: error: declaration of C function 'wxArrayShort::reverse_iterator operator+(int, const wxArrayShort::reverse_iterator&)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/longlong.h:1060: error: previous declaration 'wxULongLong operator+(long unsigned int, const wxULongLong&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/dynarray.h:993: error: declaration of C function 'wxArrayShort::reverse_iterator operator+(const wxArrayShort::reverse_iterator&, int)' conflicts with
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/dynarray.h:993: error: previous declaration 'wxArrayShort::reverse_iterator operator+(int, const wxArrayShort::reverse_iterator&)' here
/Users/blackfede/.wxMac-287-ppc//include/wx-2.8/wx/dynarray.h:993: confused by earlier errors, bailing out
make[7]: *** [libec_a-ECTag.o] Error 1
make[6]: *** [all] Error 2
make[5]: *** [all-recursive] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
PS: the autogen.sh script is not cecking properly the presence of automake 1.7 or above, by default i had 1.6, and the script doesn't complain about it.
PSS: Sure, i had updated automake before starting compilation.
-
Could anyone please try to compile a Universal Binary?
-
Don't count on me, I have only a G4, so it'll take an awful lot of time, and I'm really busy ATM.
Hopefully there are some other takers...
-
Gave it a try. after compiling all the dependencies in universal.... except libgd. which ill ignore for now, i get this error:
ldld: library not found for -lcryptopp
collect2: ld returned 1 exit status
: library not found for -lcryptopp
collect2: ld returned 1 exit status
I added both architectures to the makefile for cryptopp522 and it compiled and installed fine... so that shouldnt be the problem. but i dont have this issue with a non universal compile. So...
Heres the configure/make script i use:
cd ~/src/amule/universal/wxMac-2.8.7/build
../configure --enable-shared \
--enable-unicode \
--disable-debug \
--disable-debug_gdb \
--enable-universal_binary
make
cd ~/src/amule/universal/amule-cvs
./configure --disable-systray \
--disable-gtk \
--enable-embedded_crypto \
--enable-cas \
--enable-webserver \
--enable-amulecmd \
--without-wxdebug \
--with-wx-config=../wxMac-2.8.7/build/wx-config \
--disable-debug \
--enable-optimize \
--with-cryptopp=/usr/local/cryptopp \
--disable-dependency-tracking \
CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk" \
CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk"
make
./src/utils/scripts/mac_packager
any ideas? It compiles with the header files fine... its seems to be in the link process that the error occurs.
I guess i should add that yeah, i have 3 folders with all the right headers and the library in /usr/local/cryptopp
-
Wait, why is it trying to link dynamically? Shouldn't it link cryptopp statically, i.e. /usr/local/lib/libcryptopp.a instead of lcryptopp?
-
wuischke: It is most likely trying to link statically. Try
ld --verbose -lnonexistentto see how the linker searches for libraries.
isulzer: try adding -Wl,--verbose to the link command, this will give you a lot of information and you may be able to find out why it doesn't find -lcryptopp
-
K so the reason was: the -isysroot option forces it to use the usr folder in the 10.5 sdk which contains links to the individual libraries of /usr but not for cryptopp. It seems the -isysroot adds the prefix to --with-cryptopp=.
So you either remove the -isysroot option or you add a link or install cryptopp in the right location for it to see it.
-
K new question.... what does the --enable-static option do in the amule configure script? I get a strange ld_classic not found error when i try to use it. And when I don't use it, the packaged amule app seems to work fine when i erase all the compiled libraries(wx, cryptopp etc). These are compiled as static though, so it auto links them as static. I was wondering what happens with the dynamic libraries i have..
If this is unnecessary, then i have a working universal(all3 ppc architectures as some people still have g3s and intel) compile that should work on tiger and leopard... with the only lack being gdlib as i cant seem to get the damned thing compiled for both architectures as it has some incompatible with multi architecture compiler options... or so it tells me.
-
--enable-static will prefer static linkage over dynamic whenever both versions of a library are available. Note that this will most likely link statically to the system runtime libraries too, resulting in a HUGE executable file.
-
So its not necessary that i add this configure option? Because it does strange things to the linker... Well i can always post the package and see if people can run it without having installed those libraries...
-
k so what im getting when i add --enable-static is this:
gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -arch ppc -arch i386 -no-cpp-precomp -D_INTL_REDIRECT_MACROS -DNOPCH -W -Wall -Wshadow -Wundef -O2 -DUSE_WX_EXTENSIONS -c -o cas-cas.o `test -f 'cas.c' || echo './'`cas.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -arch ppc -arch i386 -no-cpp-precomp -D_INTL_REDIRECT_MACROS -DNOPCH -W -Wall -Wshadow -Wundef -O2 -DUSE_WX_EXTENSIONS -c -o cas-configfile.o `test -f 'configfile.c' || echo './'`configfile.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -arch ppc -arch i386 -no-cpp-precomp -D_INTL_REDIRECT_MACROS -DNOPCH -W -Wall -Wshadow -Wundef -O2 -DUSE_WX_EXTENSIONS -c -o cas-functions.o `test -f 'functions.c' || echo './'`functions.c
functions.c: In function 'get_path':
functions.c:84: warning: pointer targets in passing argument 3 of 'CFURLGetFileSystemRepresentation' differ in signedness
functions.c: In function 'get_path':
functions.c:84: warning: pointer targets in passing argument 3 of 'CFURLGetFileSystemRepresentation' differ in signedness
gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -arch ppc -arch i386 -no-cpp-precomp -D_INTL_REDIRECT_MACROS -DNOPCH -W -Wall -Wshadow -Wundef -O2 -DUSE_WX_EXTENSIONS -c -o cas-graphics.o `test -f 'graphics.c' || echo './'`graphics.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -arch ppc -arch i386 -no-cpp-precomp -D_INTL_REDIRECT_MACROS -DNOPCH -W -Wall -Wshadow -Wundef -O2 -DUSE_WX_EXTENSIONS -c -o cas-html.o `test -f 'html.c' || echo './'`html.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -arch ppc -arch i386 -no-cpp-precomp -D_INTL_REDIRECT_MACROS -DNOPCH -W -Wall -Wshadow -Wundef -O2 -DUSE_WX_EXTENSIONS -c -o cas-lines.o `test -f 'lines.c' || echo './'`lines.c
gcc -arch ppc -arch i386 -no-cpp-precomp -D_INTL_REDIRECT_MACROS -DNOPCH -W -Wall -Wshadow -Wundef -O2 -DUSE_WX_EXTENSIONS -mmacosx-version-min=10.4 -force_cpusubtype_ALL -bind_at_load -L/usr/lib -static -lpthread -o cas -framework CoreServices cas-cas.o cas-configfile.o cas-functions.o cas-graphics.o cas-html.o cas-lines.o -lz
ld_classicld_classic: for architecture ppc
ld_classic: can't locate file for: -lcrt0.o
: for architecture i386
ld_classic: can't locate file forcollect2: : -lcrt0.o
ld returned 1 exit status
collect2: ld returned 1 exit status
lipo: can't open input file: /var/folders/tJ/tJ03GWjfGIea22qP85t2CU+++TI/-Tmp-//ccfElzzU.out (No such file or directory)
make[5]: *** [cas] Error 1
There is no library installed anywhere called crt0.o however there is one called crt1.o in /usr/lib/ as well as crt2 and crt3 elsewhere... i have no idea what crt0 is or where to get it. google turns up nothing usable.
-
crt0.o should be part of the runtime libs, actually this calls ‘main()’. gcc calls it crtbegin.o. Such an error message means something very bad.
Can you compile any program (e.g. a ‘Hello World’ example) statically (i.e. gcc -static helloworld.c)?
-
nop. means something is really really screwy... ill figure it out...
-
heres what apple says:
Static linking of user binaries is not supported on Mac OS X. Tying user binaries to the internal implementation of Mac OS X libraries and interfaces would limit our ability to update and enhance Mac OS X. Instead, dynamic linking is supported (linking against crt1.o automatically instead of looking for crt0.o, for example).
We strongly recommend that you consider the limitations of statically linking very carefully, and consider your customer and their needs, plus the long-term support you will need to provide. Apple provides support and attempts to insure complete compatibility through the published APIs, but cannot insure that compatibility in a statically linked project. Any change to Mac OS X, in a system update, security update, or major revision, may break statically linked code.
If your project absolutely must link statically and need crt0.o, you can get the Csu module from Darwin and try building crt0.o statically. Please bear in mind that you must then clearly specify to your customers the compatibility risks involved in installing a product that relies on statically linked code.
I guess ill try what they say.
Although... it would probably be best to chose the static library versions manually, for everything that is necessary. how would I do this?
Oh wait never mind.. theres a ld option that makes it preffer .a over .dylib i think. ill try that...
-
Which is the option, for reference?
-
the ld thing? never mind. i misread the man file. it was an option that searched a path then looked got .dylib first, then .a. I flipped em.
some ld do come with a way to prefer static over dynamic, but not the osx version. I guess. -lLIB.a for each of the required libs should work to make it use static
-
ok. so that dosent work either. cant specify the .a as a link option. only in linker input files. Even creating a new location with only static libraries and using the -LPATH option to prefer that path.... does not work, since the osx linker prefers a dynamic lib over a static, no matter the order of the search paths. Since there are dylib versions.. id have to delete all of them... hah.
So my only solution is to add it to the linker inputs by hand? ie /opt/local/lib/libiconv.a for libiconv... does the amule configure script allow me to specify the particular library? or just the prefix? If not then i would have to manually compile and install into a directory to use with PREFIX that only had a static version....
-
k so. a manual compile/install of libiconv as static only then specified the directory with --with-libiconv-prefix= worked... least it SAYS it linked with the libiconv.a library.
-
Sorry, probably i miss the point, but why are you tring to do static link? To redistribute the aMule.app without the problem of libs dependencies? So, if this is the point, why don't use the MacOs standard way? Copy all the libs in the Framework dir in the .app bundle, then use otool to change the reference. Here (http://forum.amule.org/index.php?topic=14197.msg76708#msg76708) i've explaindex how to do.
-
because im trying to get amule to work on both tiger and leopard. Amule seems to require a later version of libiconv thats not available on the 10.4.11 system. I coupd be wrong here as i dont have tiger anymore. but a compile that works on both has to take this into account.The static compile adds very little to the binary(something like 50,000 bytes) and it fixes the cross compatibility.
-
I know that i'm a bit presompteous asking for that, but wouldn't it be possible to make a shell script that would automate all of the downloads and compile phases, and you would only have to execute it to make the whole compilation having only the Mac OS X dev tools already on the Mac...
i know it's possible, but of course, no one would do it (maybe me ?)
and i don't know if it's possible to make another shell script that would update the already compiled aMule CVS to the latest version of the common aMule CVS...
bye bye guys...
-
harlock59: check out my Xcode project for aMule. it's actually most of what you want (once its finished)
http://forum.amule.org/index.php?topic=15826.0