First off, we normally use the email@example.com list for discussion,
and reserve the svn@ list for commit emails. Now, see comments below.
On Wed, Mar 20, 2002 at 06:44:22AM -0800, Adam W. Montville wrote:
> Hi all,
> I'm new to the list and have been searching for an answer, but thought
> I'd parallelize my effort. I checked out the latest and greatest this
> morning and am now trying to build svn. Note that I have also checked
> out the latest APR and APR-UTIL packages, which are located in the apr
> and apr-util directories at the root of my subversion source tree.
> I have attempted to run the following command:
> ../configure --with-apr=<svn_src_tree_root>/apr \
> --with-apr-util=<svn_src_tree_root>/apr-util \
> --enable-maintainer-mode \
If you have apr and apr-util in the subversion source tree, you shouldn't need
to use the --with-apr[-util] switches. Our configure system should "Just
> This command fails when it tries to use the -lapr switch, presumably
> because APR and/or APR-UTIL has not yet been built. So, I have run
> buildconf, ./configure, and make in the apr directory without a
> problem. However, I cannot do the same thing with apr-util. The
> ../configure step fails when it is attempting to generate a temporary
> file. It essentially attempts to generate some temporary file that it
> cannot parse -- it creates a bad temporary file. With high hopes,
> however, I've been continuing on...
Not sure what is happening here, I've never had a problem with it.
> With the APR built, and the APR-UTIL still in the air, I tried to run
> the above ./configure command again -- it worked! However, when I try
> to make, the following error arises:
> In file included from subversion/bindings/swig/swigutil.c:24:
> subversion/bindings/swig/swigutil.h:33:20: Python.h: No such file or
> subversion/bindings/swig/swigutil.c:28:20: Python.h: No such file or
> make: *** [subversion/bindings/swig/swigutil.lo] Error 1
I'm not really up on the swig bindings stuff, so I'm at a loss here. I do
know that if configure can't find swig, it won't try to build that stuff, so
maybe removing swig from your path will help (unless you planned to use the
swig stuff :).
> I understand perfectly well what it all means, but I'm wondering how I'm
> supposed to resolve it, especially when I have Python installed on my
I would guess that it is a swig issue, maybe you don't have the latest and
greatest swig installed, or it is installed in a non-standard way, and we're
not picking up its include paths properly.
> Any help is appreciated.
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
Received on Wed Mar 20 16:06:24 2002
- application/pgp-signature attachment: stored