On Monday 13 August 2007 14:50, Judd Montgomery wrote: > On Mon, August 13, 2007 12:30 am, TR wrote: > > I'm trying to generate a working "configure" script from the CVS source. > > If > > someone could point out what I may be doing wrong, it would be > > appreciated. > > > > -TR > > Did you try ./autogen.sh? > > Judd > Thanks, Judd. Ja - same result - choking on: 3300: echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5 Which gives the following output: checking for library containing strerror... none required ./configure: line 3300: syntax error near unexpected token `echo' ./configure: line 3300: `echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5' ++ exit 1 Here are a few lines above the offending one in the generated "configure" script: ... test "$ac_cv_search_strerror" = "none required" || LIBS="$ac_cv_search_strerror $LIBS" fi AC_PROG_INTLTOOL() # Find a good install program. We prefer a C program (faster), # so one script is as good as another. But avoid the broken or # incompatible versions: # SysV /etc/install, /usr/sbin/install # SunOS /usr/etc/install # IRIX /sbin/install # AIX /bin/install # AmigaOS /C/install, which installs bootblocks on floppy discs # AIX 4 /usr/bin/installbsd, which doesn't work without a -g flag # AFS /usr/afsws/bin/install, which mishandles nonexistent args # SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff" # OS/2's system install, which has a completely different semantic # ./install, which can be erroneously created by make from ./install.sh. 3300: echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5 echo $ECHO_N "checking for a BSD-compatible install... $ECHO_C" >&6 sh-3.00$ This is the first package I've tried to build without a prebuilt "configure" so I can't say whether it's a problem on my installation. Perhaps I'll try checking out an earlier version of JPilot, or some other CVS code, to check it out. -TR
More information about the jpilot mailing list