On 4/16/07, nobu / ruby-lang.org <nobu / ruby-lang.org> wrote:
> Hi,
>
Hello
>
> Do you consider that -L. always should take precedence to other
> linker flags?
Yes, because otherwise libraries already in the system could be linked
instead of the libraries in the build directory. There could be
similar problem with extension build that is not apparent because the
libraries are compatible enough.
>
>
> Index: configure.in
> ===================================================================
> --- configure.in        (revision 12175)
> +++ configure.in        (working copy)
> @@ -150,4 +150,9 @@ fi
>  AC_PROG_CC
>  AC_PROG_GCC_TRADITIONAL
> +if test "$GCC" = yes; then
> +    linker_flag=-Wl,
> +else
> +    linker_flag=
> +fi
>
>  RUBY_PROG_GNU_LD
> @@ -1392,12 +1397,8 @@ if test "$enable_shared" = 'yes'; then
>  fi
>  if test "$enable_rpath" = yes; then
> -    if test "$GCC" = yes; then
> -       LIBRUBYARG_SHARED='-Wl,-R -Wl,$(libdir) -L$(libdir) -L. '"$LIBRUBYARG_SHARED"
> -    else
> -       LIBRUBYARG_SHARED='-R $(libdir) -L$(libdir) -L. '"$LIBRUBYARG_SHARED"
> -    fi
> +    LIBRUBYARG_SHARED="${linker_flag}-R ${linker_flag}\$(libdir) -L. -L\$(libdir) $LIBRUBYARG_SHARED"
>  fi
>
> -XLDFLAGS="$XLDFLAGS -L."
> +LDFLAGS="-L. $LDFLAGS"
>  AC_SUBST(ARCHFILE)
>
>

This patch fixes my build issue and appears better than just swapping the flags.

Thanks

Michal