On 15-May-09, at 7:17 PM, Stefan Sperling wrote:
> On Fri, May 15, 2009 at 06:11:23PM -0400, Scott Palmer wrote:
>> On Thu, May 14, 2009 at 8:48 AM, Stefan Sperling <stsp_at_elego.de>
>> So I guess your options are:
>> A 1) Use a newer APR (i.e. get it from trunk and hope it'll work)
>> A 2) Install libtool 1.5 somewhere and use that to build
>> A 3) Install the libapr1-dev package provided by Ubuntu instead
>> A A compiling APR yourself. There's also debug symbols in
>> A A if you need them.
>> A 4) Wait for new APR release and hope it'll fix this.
>> Tried option 1, much better... but still fails..
> Why option 1?
> Why don't you just use the libapr1-dev package?
Because it was first? It was natural to work through the list of
options you gave me in order. But I didn't have time to "create a
huge pile of work" so I stopped when #1 failed.
Because I don't even know what libtool is. I have no idea how I would
acquire an older version and place it "somewhere" and manage to have
it used by the build scripts instead of the version I already have (at
least not without getting into an ugly mess)
Because the output of ./configure directed me to pull apr and apr-util
from subversion and, that was a lot easier than guessing "libapr1-dev"
Option 4 happens by default as I try other things.
> You should try to resolve as many dependencies from your distribution
> as possible.
Easier said than done, when you have to guess at the names of the
packages you need.
> Anything else creates a huge pile of work.
I agree. I've found myself in the midst of that "huge pile" numerous
> You're already compiling Subversion yourself. That's enough trouble
> already. Just go for option 3 unless you have a really good reason
> not to do so.
> Well, if you really need to build your own APR, what I'd do is:
> aptitude search expat
> and then look for packages that end in -dev. Like this one:
> libexpat1-dev - XML parsing C library - development kit
> Install that package, and APR's configure script should
> pick up expat automatically, like magic.
This is making the huge assumption that I know that "expat" is more
than just the name of a folder.
>> This happens all the time. I'm basically hitting the wall that I
>> inevitably hit when trying to get anything done on Linux -
> I'm basically hitting a wall whenever I'm trying to get anything done
> on anything that's neither Linux nor *BSD. It all amounts to what
> used to.
To a degree. Though it's telling that you never find complicated (and
somewhat ridiculous) ./configure scripts on Windows... Scripts that
apparently are supposed to figure all this stuff out for you, and
instead, as I have demonstrated, fail miserably. (And for the record,
in my experience, they fail often.) The need for ./configure is strong
evidence in my favour that it's *nix that is the overly complex
disaster.. and trust me I can't stand Windows, I develop on it all
day, luckily in Java so I don't go insane with win32 :-)... and I am
trying to use Linux after all ;-) My other computer is a Mac where
stuff "just works", sometimes even the unixy stuff, like ./configure,
though in this case macports was up to date so getting 1.6.2 on the
Mac was simple.
On on the Mac now, I'll try the other options in a few minutes...
thanks for the help!
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-16 02:24:44 CEST