Re: [m32c] build libstdc++; combined builds, libssp, and libgloss.

[Rask Ingemann Lambertsen <rask at sygehus dot dk>]

On Tue, Apr 18, 2006 at 08:55:03PM -0400, DJ Delorie wrote:
> 
> m32c can build libstdc++-v3 now, so no reason to hold it back any more.
> 
> libssp needs to link an executable during configure (which seems wrong
> to me, but outside the scope of this patch).  The m32c can't link
> executables until libgloss is installed (crt0, libnosys, and r8c.ld
> are needed), and libssp can't have GCC_NO_EXECUTABLES because it needs
> to(?) test some things about shared libraries (libstdc++-v3 doesn't
> seem to have this problem).

   These days, libstdc++-v3 does have the same problem. This is what lead me
to open PR other/32154.

> So, this patch adds a bunch of flags-for-target to make linking
> against an in-tree libgloss work.  Committed.

   This went in as revision 113066:

> Index: configure.in
[...]
> @@ -2129,6 +2126,20 @@ if test "x${use_gnu_ld}" = x &&
>    FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -L$$r/$(HOST_SUBDIR)/ld'
>  fi
>  
> +# Search for other target-specific linker scripts and such.
> +case "${target}" in
> +  m32c-*-* )
> +    if test -d ${srcdir}/libgloss/m32c; then
> +      # This is for crt0.o
> +      FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -B$$r/$(TARGET_SUBDIR)/libgloss/m32c'
> +      # This is for r8c.ld
> +      FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -L$$r/$(TARGET_SUBDIR)/libgloss/m32c'
> +      # This is for libnosys.a
> +      FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -L$$r/$(TARGET_SUBDIR)/libgloss/libnosys'
> +    fi
> +    ;;
> +esac
> +
>  # Makefile fragments.
>  for frag in host_makefile_frag target_makefile_frag alphaieee_frag ospace_frag;
>  do

   Why don't we do this for all the newlib targets, instead of just for
m32c-*-*? Is there a particular reason for not doing so when --with-newlib
is specified?

-- 
Rask Ingemann Lambertsen