thanks again for your help.
I think there was a misunderstanding on my side.
Before I downloaded the SVN code, I already installed SVN as a user
installation. Therefore I already had some libs in my "/usr/local/
When I built the SVN libs via the source I've donwloaded later, I did
not know that they are put into hidden ".libs" folders. So when I
looked into the "/usr/local/lib" folder, I thought that these were
the libraries I've built. That's also the reason why they where fat
libs - universal.
In the meantime I found out the locations of the built l.ibs and put
them togehter. As you said: They're not fat but either ppc or i386.
Compiling and linking with those static libs was finally successful.
Of course, only for one architecture. The linker was still
complaining, that some "libiconv", "libiconv_open" and
"libiconv_close" stuff is still missing.
I finally solved that by adding the "libiconv.dylib" from "/usr/lib/"
to the project. I'm not sure if that is the right way, but at least
it is linking now.
However, since I need a universal App, I tried to create universal
binaries. After building the svn-libs on both architectures, I tried
to create fat libs via the "lipo -create" command. This worked fine
so far, at least "lipo -info" states that all the libraries are fat
and contain both "ppc" and "i386" code.
But if I try to link a universal project with them, on the PPC the
linker complains that the i386 part is missing, while on a MacIntel
it complains that the PPC part is missing. So finally both parts seem
to be included, but the linker can only find its native part.
OK, this seems to be more a Mac-specific problem and it may not be
posted here on the Subversion mailing list. But if anybody has
already had the same problem and knows about a solution, please don't
hesitate to tell me please.
Am 12.09.2007 um 11:53 schrieb Jeremy Pereira:
> On 11 Sep 2007, at 15:56, B. Blodau wrote:
>> Hi Jeremy,
>> thanks a lot for your help.
>> I already tried to use the static libraries instead of the dynamic
>> ones, but they seem to be incomplete. At least with my
>> installation of the 1.4.4 version, there are no libapr, libaprutil
>> static libraries.
> On my installation they seem to be in the Apache installation
> directory. But there are also copies in <subversion source dir>/
> apr/.libs and <subversion source dir>/apr-util/.libs.
>> Building them via the source code, results in compiler errors for
>> at least xmltok_impl.c, which is part of the apr-utils. I'm
>> wondering which compiler settings may be necessary to compile it.
> Here's my configure string:
> ./configure PYTHON=/usr/bin/python --with-apxs=/usr/local/apache2/
> bin/apxs --with-berkeley-db=/usr/local/BerkeleyDB.4.3 --with-ssl --
> with-editor=vi --with-swig=/usr/local/bin/swig
> I have Apache 2.0.something installed in /usr/local/apache2 and BDB
> 4.3 installed in /usr/local/BerkeleyDB.4.3. With those settings,
> Subversion builds cleanly on my Mac. NB you don't actually need
> the --with-swig switch or the --with-editor switch or probably the
> PYTHON=.... bit.
>> In the neon project I'm also getting compiler errors, that - e.g.
>> - gnutls.h can't be found. Do I have to install anything else?
> I don't have that anywhere on my file system but subversion builds
> fine for me.
>> If in your case, using the souce is straight forward, would may I
>> do wrong? I just set up an XCode project for a tool and added the
>> include paths and the code and it should work fine.
> Are you trying to using XCode to build all of subversion? It's
> better to just follow the build instructions in the INSTALL file in
> the source distribution.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Sep 14 14:09:03 2007