ruby autoconf problems

Hello

I noticed problems building ruby on OS X after changing from
autoconf
2.60 to 2.61.

As I patch the configure script to name the libruby the way
I want,
and build extensions with the linker flags I want, I
regenerate the
configure each time.

It appears the shipped configure is pregenerated with an
older
autoconf but generating with a newer one breaks the build.

For me  the doubly quoted LIBPATHFLAG=' -L"%s"'
receives additional
quoting with the new autoconf.


I suspect this is because the variable is not really
expanded by
autoconf but is ripped from an autoconf-internal
config.status by a
script to make rbconfig.rb, and the format of this file
changed.


Thanks

Michal

Hi,

At Thu, 22 May 2008 19:26:53 +0900,
Michal Suchanek wrote in [ruby-core:16839]:
> As I patch the configure script to name the libruby the
way I want,
> and build extensions with the linker flags I want, I
regenerate the
> configure each time.

What revision are you using?

> For me  the doubly quoted LIBPATHFLAG='
-L"%s"' receives additional
> quoting with the new autoconf.

LIBPATHFLAG in rbconfig has double qoutes, or empty?  It
should
be defaulted to ' -L%s' now.

-- 
Nobu Nakada

On 22/05/2008, Nobuyoshi Nakada <noburuby-lang.org> wrote:
> Hi,
>
>  At Thu, 22 May 2008 19:26:53 +0900,
>  Michal Suchanek wrote in [ruby-core:16839]:
>
> > As I patch the configure script to name the
libruby the way I want,
>  > and build extensions with the linker flags I
want, I regenerate the
>  > configure each time.
>
>
> What revision are you using?

Ruby 1.8.6-p111
>
>
>  > For me  the doubly quoted LIBPATHFLAG='
-L"%s"' receives additional
>  > quoting with the new autoconf.
>
>
> LIBPATHFLAG in rbconfig has double qoutes, or empty? 
It should
>  be defaulted to ' -L%s' now.

Yes, that's how I worked around the build problem.
I will try p114.

Thanks

Michal

Hi,

At Fri, 23 May 2008 10:33:44 +0900,
Michal Suchanek wrote in [ruby-core:16860]:
> >  > For me  the doubly quoted LIBPATHFLAG='
-L"%s"' receives additional
> >  > quoting with the new autoconf.
> >
> >
> > LIBPATHFLAG in rbconfig has double qoutes, or
empty?  It should
> >  be defaulted to ' -L%s' now.
> 
> Yes, that's how I worked around the build problem.
> I will try p114.

r12205 and r15557 haven't been backported to 1.8.6 yet.

-- 
Nobu Nakada

Michal Suchanek wrote:
> Nobuyoshi Nakada wrote:
>> LIBPATHFLAG in rbconfig has double qoutes, or
empty?  It should
>>  be defaulted to ' -L%s' now.
> Yes, that's how I worked around the build problem.
> I will try p114.

Since you're working with the configure.ac, maybe you'd have
time
verify this fixes autoconf 2.62? I ran into autoconf stuff
with
macports portfile. With both p111 and p114, an autoconf 2.62
pass
would break the config.status so many standard libraries
aren't built.
I would love to fix, but my autoconf foo is weak.

http:// Joseph Holsten .com

On 23/05/2008, Joseph Holsten <josephjosephholsten.com> wrote:
> Michal Suchanek wrote:
>
> > Nobuyoshi Nakada wrote:
>  >> LIBPATHFLAG in rbconfig has double qoutes, or
empty?  It should
>  >>  be defaulted to ' -L%s' now.
>  > Yes, that's how I worked around the build
problem.
>  > I will try p114.
>
>
> Since you're working with the configure.ac, maybe you'd
have time
>  verify this fixes autoconf 2.62? I ran into autoconf
stuff with
>  macports portfile. With both p111 and p114, an
autoconf 2.62 pass
>  would break the config.status so many standard
libraries aren't built.
>  I would love to fix, but my autoconf foo is weak.

For me the fix was removing the double quotes from
LIBPATHFLAG.

That is change it from ' -L"%s"' to ' -L%s' in
configure.in.

Not that I really understand autoconf.

Thanks

Michal