Re: busted 'make swig-py'...

On Fri, Feb 28, 2003 at 10:57:45AM -0800, Ben Collins-Sussman wrote:
> Matt Kraai <kraai@alumni.cmu.edu> writes:
>
> > > $ make swig-py
> > > /usr/local/bin/swig -c -python -noproxy -I/home/sussman/projects/svn2/subversion/bindings/swig -I/home/sussman/projects/svn2/subversion/include -I/usr/local/apache2/include -I/usr/local/include/python2.2 -o subversion/bindings/swig/python/svn_client.c
> > > Must specify an input file. Use -help for available options.
> > > *** Error code 1
> > >
> > > And here's what I discovered: if I now run 'gmake swig-py', everything
> > > works. And then *afterwards*, plain old 'make swig-py' works for me!
> > >
> > > Anyone have any ideas? Wanna see my generated build files?
> >
> > Since it's dropping the last part of the command, could you be
> > running into a maximum line length restriction?
>
> No way. The build system runs commands like this all the time:
>
> cd subversion/clients/cmdline && /usr/local/bin/bash /home/sussman/projects/svn2/libtool --silent --mode=link gcc -g -Wall -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -pthread -DNEON_ZLIB -Wpointer-arith -Wwrite-strings -Wshadow -DSVN_DEBUG -DAP_DEBUG -L/usr/local/lib -rpath /usr/local/lib -o svn add-cmd.o cat-cmd.o checkout-cmd.o cleanup-cmd.o commit-cmd.o copy-cmd.o delete-cmd.o diff-cmd.o export-cmd.o feedback.o help-cmd.o import-cmd.o info-cmd.o log-cmd.o ls-cmd.o main.o merge-cmd.o mkdir-cmd.o move-cmd.o prompt.o propdel-cmd.o propedit-cmd.o propget-cmd.o proplist-cmd.o props.o propset-cmd.o resolve-cmd.o revert-cmd.o status-cmd.o status.o switch-cmd.o update-cmd.o util.o ../../../subversion/libsvn_client/libsvn_client-1.la ../../../subversion/libsvn_wc/libsvn_wc-1.la ../../../subversion/libsvn_ra/libsvn_ra-1.la ../../../subversion/libsvn_delta/libsvn_delta-1.la ../../../subversion/libsvn_subr/libsvn_subr-1.la ../../../subversion/libsvn_auth/libs!
> vn_auth-1.la /usr/local/apache2/lib/libaprutil-0.la -lexpat /usr/local/apache2/lib/libapr-0.la -lm -lcrypt -L/usr/local/lib -lneon -lz -L/usr/local/lib -lxml2 -lz -L/usr/local/lib -liconv -lm -L/usr/local/lib
>
> I think Mike is right. BSD make doesn't know how to create a .c from
> a .i file, but GNU make does.

I have

 subversion/bindings/swig/python/svn_client.c: subversion/bindings/swig/svn_client.i
         $(RUN_SWIG_PY)

in my build-outputs.mk and

 RUN_SWIG_PY = $(SWIG) -c -python -noproxy $(SWIG_INCLUDES) $(SWIG_PY_INCLUDES) -o $@ $<

in my Makefile, so we are telling it how to create the .c for the
.i. Furthermore, the command line you sent shows it running the
command (except for the $<).

Matt

-- 
Oink!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org