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

Re: Error running configure for subversion 1.7.0

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 18 Oct 2011 03:04:52 +0200

I suppose setting SHELL or CONFIG_SHELL to bash or /usr/xpg4/bin/sh on
the configure command line might have had a similar effect.

Ed Hillmann wrote on Tue, Oct 18, 2011 at 09:42:39 +1000:
> I found a much easier solution. I changed the first line of the configure
> script from
>
> #!/bin/ksh
>
> to
>
> #!/bin/bash
>
> Everything worked straight away. :)
>
> Thanks,
> Ed
>
> On Mon, Oct 17, 2011 at 7:42 AM, Ed Hillmann <ed.hillmann_at_gmail.com> wrote:
>
> > I spoke too soon.
> >
> > Changing printf to echo $output_flags did work. I just needed to do it for
> > all of the occurences in the script.
> >
> > So, I'm making forward progress. Thanks!
> >
> > Ed
> >
> > On Fri, Oct 14, 2011 at 6:59 PM, Philip Martin <philip.martin_at_wandisco.com
> > > wrote:
> >
> >> Ed Hillmann <ed.hillmann_at_gmail.com> writes:
> >>
> >> > checking for a BSD-compatible install... build/install-sh -c
> >> > configure: Apache Portable Runtime (APR) library configuration
> >> > checking for APR... yes
> >> > checking APR version... 1.4.5
> >> > /u01/ct/ctapp/subversion-1.7.0/configure: bad substitution
> >> >
> >> >
> >> > I can't see what is causing the bad substitution error.
> >>
> >> > printf "%s" "${output_flags# }"
> >>
> >> I'm guessing it's the # substitution in that line. Which shell are you
> >> using? It's a long time since I used Solaris but there used to be
> >> /usr/xpg4/bin/sh that was more like the shells commonly found on Linux.
> >> Perhaps you could use that. Alternatively you may be able to replace
> >> the above line with:
> >>
> >> echo $output_flags
> >>
> >> it occurs in several places in configure.
> >>
> >> --
> >> Philip
> >>
> >
> >
Received on 2011-10-18 03:05:39 CEST

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

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