On Fri, 2004-06-18 at 11:04, Ben Reser wrote:
> *nod* I knew there would be issues. But if I didn't do it we wouldn't
> see them. :)
Yup, that's why it's /trunk! No time like the present to work these
things out.
> > In file included from
> > /home/sussman/projects/svn/subversion/bindings/swig/perl/libsvn_swig_perl/swigutil_pl.c:20:
> > /usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE/perl.h:3310: warning:
> > declaration of `exp' shadows a global declaration
> > /usr/include/bits/mathcalls.h:101: warning: shadowed declaration is here
> >
> > (...I also get that warning for symbols 'floor' and 'send'...)
>
> The above errors are something I can't do a darn thing about. Perl has
> functions of the same name as some various functions that we get from
> the C library. The warnings are actually coming from headers that are
> outside of our project. Yes, they annoy me greatly. But I can't see
> anyway to get rid of them.
Arghh. We've actually received compliments from outsiders about how
Subversion's code base is so clean, that we're "the only project they've
ever seen where ./configure && make produces no warnings at all."
According to Fitz, I believe Apple Computer(?) once compiled Subversion
source in a presentation for exactly that reason. :-)
I'd hate to blow that reputation.
Is 'make' building the exact same set of things for swig/perl as it does
for swig/python? That is, just the glue libraries, and nothing else?
If it's also building the "meat" of the bindings, perhaps we can push
that into a separate rule, the same way we do with 'make swig-py'?
I'm just grasping at straws here.
>
> > In file included from /usr/local/apache2/include/apr_thread_proc.h:64,
> > from /usr/local/apache2/include/apr_portable.h:68,
> > from
> > /home/sussman/projects/svn/subversion/bindings/swig/perl/libsvn_swig_perl/swigutil_pl.c:27:
> > /usr/local/apache2/include/apr_file_io.h:624: warning: `PerlIO_stdoutf'
> > is an unrecognized format function type
> >
> > (...I get the same warning for apr_strings.h and svn_io.h...)
>
> Humm I haven't seen this one before. Nor can I replicate this. Can you
> send me the full log of your build? What I don't get is we don't even
> use PerlIO_stdoutf.
Will do.
>
> > Finally, when I run 'make' and there's nothing to do, I still get
> > screen spam:
> >
> > $ make
> > cd /home/sussman/projects/svn/subversion/bindings/swig/perl/native; make
> > make[1]: Entering directory
> > `/home/sussman/projects/svn/subversion/bindings/swig/perl/native'
> > make[1]: Leaving directory
> > `/home/sussman/projects/svn/subversion/bindings/swig/perl/native'
> >
> > $
> >
> > Can we shut that feedback off? I have to admit, I've become spoiled.
> > Automake generates that kind of 'entering/leaving directory' noise,
> > but I've gotten used to the golden silence of our single Makefile.
>
> Yeah, I was going to try and find a way to turn this off. I just
> haven't gotten to it yet. :)
Cool, thanks. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 18 18:18:06 2004