[Bug libstdc++/11193] New: Version 1.126 of libstdc++-v3/configure.in broke pre-installed newlib builds

[Bug libstdc++/11193] New: Version 1.126 of libstdc++-v3/configure.in broke pre-installed newlib builds

[hp@gcc.gnu.org]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193

           Summary: Version 1.126 of libstdc++-v3/configure.in broke pre-
                    installed newlib builds
           Product: gcc
           Version: 3.4
            Status: UNCONFIRMED
          Keywords: build
          Severity: normal
          Priority: P2
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hp@gcc.gnu.org
                CC: bkoz@redhat.com,gcc-bugs@gcc.gnu.org
 GCC build triplet: Canadians are supposedly safe from harm by this bug.
  GCC host triplet: (any cross host)
GCC target triplet: (any newlib target, e.g. most *-*-elf)

Building libstdc++-v3 against already installed newlib doesn't work anymore
since rev 1.126 of libstdc++-v3/configure.in.  See discussion at
<URL:http://gcc.gnu.org/ml/gcc-patches/2003-06/msg00321.html>.

[Bug libstdc++/11193] Version 1.126 of libstdc++-v3/configure.in broke pre-installed newlib builds

[steven at gcc dot gnu dot org]

------- Additional Comments From steven at gcc dot gnu dot org  2003-12-21 01:02 -------
This bug was opened more than six months ago, is still in UNCONFIRMED state,  
and has an empty audit trail.  Can someone confirm that this problem report 
still is relevant, and if so, confirm the bug? 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193

[Bug libstdc++/11193] Version 1.126 of libstdc++-v3/configure.in broke pre-installed newlib builds

[hp at gcc dot gnu dot org]

------- Additional Comments From hp at gcc dot gnu dot org  2003-12-21 03:20 -------
I confirmed this with LAST_UPDATED: Sun Dec 21 02:22:13 UTC 2003
using the following steps:

1. Configure in /home/hp/cvs_areas/combined/mno
   using combined sources:
&& make all && make install

2. rm -rf /home/hp/cvs_areas/combined/combined/newlib \
 /home/hp/cvs_areas/combined/combined/libgloss 

3. Configure in /home/hp/cvs_areas/combined/mnx:
   /home/hp/cvs_areas/combined/combined/configure --prefix=/tmp/mnp \
 --target=mn10300-elf --enable-languages=c++ && make all

4. Observe build failure as reported.  Last 10 lines in section
 "Configuring in mn10300-elf/libstdc++-v3" pasted as follows:

checking for enabled long long I/O support... yes
checking for thread model used by GCC... single
configure: Debug build flags set to -g3 -O0
checking for additional debug build... no
checking for extra compiler flags for building...
configure: WARNING: No native atomic operations are provided for this platform.
configure: WARNING: They cannot be faked when thread support is disabled.
configure: WARNING: Thread-safety of certain classes is not guaranteed.
configure: error: No support for this host/target combination.
make: *** [configure-target-libstdc++-v3] Error 1


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|0000-00-00 00:00:00         |2003-12-21 03:20:52
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193

[Bug libstdc++/11193] Version 1.126 of libstdc++-v3/configure.in broke pre-installed newlib builds

[hp at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|2003-12-21 03:21:41         |2003-12-21 03:23:02
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193

[Bug libstdc++/11193] Version 1.126 of libstdc++-v3/configure.in broke pre-installed newlib builds

[hp at gcc dot gnu dot org]

------- Additional Comments From hp at gcc dot gnu dot org  2003-12-21 03:28 -------
Sorry, X cut-buffer pasto; step 1 should be:
1. Configure in /home/hp/cvs_areas/combined/mno
   using combined sources:
/home/hp/cvs_areas/combined/combined/configure --prefix=/tmp/mnp \
 --target=mn10300-elf --enable-languages=c++ && make all && make install

I.e. as step 3 but adding "&& make install".

(It seems I can't set bug state to CONFIRMED.  Please?)

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2003-12-21 03:24:13         |2003-12-21 03:28:53
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193

[Bug libstdc++/11193] [3.4 Regression] The conversion to autoconf 2.5 broke pre-installed newlib builds

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-14 04:51 -------
Better summary so that someone who know libstdc++'s configure can help out.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[3.4 Regression] Version    |[3.4 Regression]  The
                   |1.126 of libstdc++-         |conversion to autoconf 2.5
                   |v3/configure.in broke pre-  |broke pre-installed newlib
                   |installed newlib builds     |builds


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193

[Bug libstdc++/11193] [3.4 Regression] The conversion to autoconf 2.5 broke pre-installed newlib builds

[hp at bitrange dot com]

------- Additional Comments From hp at bitrange dot com  2004-01-14 21:53 -------
Subject: Re:  [3.4 Regression]  The conversion to autoconf
 2.5  broke pre-installed newlib builds

On Tue, 14 Jan 2004, pinskia at gcc dot gnu dot org wrote:

>
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-14 04:51 -------
> Better summary so that someone who know libstdc++'s configure can help out.

No.  Your changed summary is now incorrect.  It wasn't an
automake 2.5 conversion that was the reason for revision 1.126,
it was PR 3066.  Please fix.

>
> --
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Summary|[3.4 Regression] Version    |[3.4 Regression]  The
>                    |1.126 of libstdc++-         |conversion to autoconf 2.5
>                    |v3/configure.in broke pre-  |broke pre-installed newlib
>                    |installed newlib builds     |builds
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193

[Bug libstdc++/11193] [3.4 Regression] revision 1.126 of configure.in broke pre-installed newlib builds

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-14 22:03 -------
I had looked at the diff it said was it needed autoconf 2.5 (I must have looked at the diff wrong).

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[3.4 Regression]  The       |[3.4 Regression] revision
                   |conversion to autoconf 2.5  |1.126 of configure.in  broke
                   |broke pre-installed newlib  |pre-installed newlib builds
                   |builds                      |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193

[Bug libstdc++/11193] [3.4/3.5 Regression] revision 1.126 of configure.in broke pre-installed newlib builds

[ljrittle at gcc dot gnu dot org]

------- Additional Comments From ljrittle at gcc dot gnu dot org  2004-02-06 03:56 -------
An expert for this target needs to add a section for (e.g.) mn10300-elf to
crossconfig.m4 (and as this problem does not affect all cross configurations,
even some that use newlib, I've updated the Target window above).

We now mandate that all crosses be named explicitly in crossconfig.m4
due to past issues. The only unfortunate factor is that this is not reported
until the secondary configuration steps after gcc bootstraps...

As we now consider this working as expected (i.e. the error is reporting
the true state of affairs), marking as WONTFIX (mirrors Benjamin's comments
in thread).


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
 GCC target triplet|(any newlib target, e.g.    |(any not named in
                   |most *-*-elf)               |crossconfig.m4)
         Resolution|                            |WONTFIX


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193