[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Cannot configure

From: Kobayashi Noritada <nori1_at_dolphin.c.u-tokyo.ac.jp>
Date: 2005-01-29 00:34:06 CET


From: Philip Martin <philip@codematters.co.uk>
Subject: Re: Cannot configure
Date: Fri, 28 Jan 2005 21:33:40 +0000

> > checking for apr_int64_t Python/C API format string... CPPFLAGS: -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -I/home/nori1/svnwc/subversion-ruby/apr/include
> Print $CPP, it should be something like "gcc -E".

Yes, like this:

  CPP: gcc -E

> > configure: error: failed to recognize APR_INT64_T_FMT on this platform
> >
> > The former is the same, but the latter is different.
> > There is one '-I'; in $CPPFLAGS an -I is included until the last.
> > So -I is always present, but APR_INT64_T_FMT is not detected.
> Does config.log still report "apr.h: No such file or directory"?

Sorry for forgetting to report about it.
config.log do not report any more.

  configure:11844: checking for apr_int64_t Python/C API format string
  configure:11897: result:
  configure:11901: error: failed to recognize APR_INT64_T_FMT on this platform

> Create a file.c containing the two lines
> #include <apr.h>
> and you can run the failing command by hand, something like:
> $ gcc -E -I /home/nori1/svnwc/subversion-ruby/apr/include file.c | grep 'MaTcHtHiS "lld" EnDeNd'
> It's expected to result in one line of output:
> MaTcHtHiS "lld" EnDeNd

But this manual operation also fails; no line in output.

|:  Noritada KOBAYASHI
|:  Dept. of General Systems Studies,
|:  Graduate School of Arts and Sciences, Univ. of Tokyo
|:  E-mail: nori1@dolphin.c.u-tokyo.ac.jp (preferable)
|:          nori@esa.c.u-tokyo.ac.jp
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 29 00:35:23 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.