Bug#176311: gcc-3.2: configure generated from broken libtool.m4
Benjamin Kosnik writes:
> On Sun, 12 Jan 2003 11:25:04 +0100
> Matthias Klose <[EMAIL PROTECTED]> wrote:
>
> >Is it likely this will be addressed in the gcc-3.2 branch?
>
> Are you volunteering?
Ryan Murray provided a patch, which I attach here. Needed for the 3.3
branch as well. checked on mips{,el}-linux and i386-linux only.
The patch touches a few Makefile.am's to remove the
--tag option to libtool (doesn't exist), and then uses autoreconf on the
subdirs, and copies in things to the top level.
gnu automake)
After applying the patch:
libtoolize --force --copy
cp /usr/share/aclocal/libtool.m4 . # (from libtool-1.4.3)
for i in libf2c libjava/libltdl libobjc libstdc++-v3 zlib; do
(cd ${i} ; autoreconf --force)
done
--- libstdc++-v3/libmath/Makefile.am2002-09-12 22:25:57.0 -0700
+++ libstdc++-v3/libmath/Makefile.am2003-01-22 03:00:53.0 -0800
@@ -40,5 +40,3 @@
INCLUDES = \
$(TOPLEVEL_INCLUDES)
-# Only compiling "C" sources in this directory.
-LIBTOOL = @LIBTOOL@ --tag CC
\ No newline at end of file
--- libstdc++-v3/libsupc++/Makefile.am 2003-01-22 03:27:55.0 -0800
+++ libstdc++-v3/libsupc++/Makefile.am 2003-01-22 04:13:44.0 -0800
@@ -125,7 +125,7 @@
$(C_COMPILE) -DIN_GLIBCPP_V3 -Wno-error -c $<
# LTCOMPILE is copied from LTCXXCOMPILE below.
-LTCOMPILE = $(LIBTOOL) --tag CC --tag disable-shared --mode=compile $(CC) \
+LTCOMPILE = $(LIBTOOL) --mode=compile $(CC) \
$(DEFS) $(GCC_INCLUDES) \
$(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(AM_CXXFLAGS)
@@ -166,7 +166,7 @@
#
# We have to put --tag disable-shared after --tag CXX lest things
# CXX undo the affect of disable-shared.
-LTCXXCOMPILE = $(LIBTOOL) --tag CXX --tag disable-shared \
+LTCXXCOMPILE = $(LIBTOOL) \
--mode=compile $(CXX) $(INCLUDES) \
$(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(AM_CXXFLAGS)
@@ -176,7 +176,7 @@
# course is problematic at this point. So, we get the top-level
# directory to configure libstdc++-v3 to use gcc as the C++
# compilation driver.
-CXXLINK = $(LIBTOOL) --tag CXX --tag disable-shared \
+CXXLINK = $(LIBTOOL) \
--mode=link $(CXX) \
@OPT_LDFLAGS@ @SECTION_LDFLAGS@ $(AM_CXXFLAGS) $(LDFLAGS) -o $@
--- libstdc++-v3/src/Makefile.am2003-01-22 04:30:51.0 -0800
+++ libstdc++-v3/src/Makefile.am2003-01-22 05:04:05.0 -0800
@@ -177,7 +177,7 @@
# correct solution is to add `--tag CXX' to LTCXXCOMPILE and maybe
# CXXLINK, just after $(LIBTOOL), so that libtool doesn't have to
# attempt to infer which configuration to use
-LTCXXCOMPILE = $(LIBTOOL) --tag CXX --mode=compile $(CXX) $(INCLUDES) \
+LTCXXCOMPILE = $(LIBTOOL) --mode=compile $(CXX) $(INCLUDES) \
$(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(AM_CXXFLAGS)
# 3) We'd have a problem when building the shared libstdc++ object if
@@ -186,7 +186,7 @@
# course is problematic at this point. So, we get the top-level
# directory to configure libstdc++-v3 to use gcc as the C++
# compilation driver.
-CXXLINK = $(LIBTOOL) --tag CXX --mode=link $(CXX) \
+CXXLINK = $(LIBTOOL) --mode=link $(CXX) \
@OPT_LDFLAGS@ @SECTION_LDFLAGS@ $(AM_CXXFLAGS) $(LDFLAGS) -o $@
install-exec-local:
--- libjava/Makefile.am 2003-01-22 05:09:24.0 -0800
+++ libjava/Makefile.am 2003-01-22 05:12:36.0 -0800
@@ -71,15 +71,15 @@
## compiles.
GCJ_WITH_FLAGS = $(GCJ) --encoding=UTF-8
-GCJCOMPILE = $(LIBTOOL) --tag=GCJ --mode=compile $(GCJ_WITH_FLAGS)
-fclasspath= -fbootclasspath=$(here) $(JC1FLAGS) -MD -MT $@ -MF $(@:.lo=.d) -c
-GCJLINK = $(LIBTOOL) --tag=GCJ --mode=link $(GCJ) -L$(here) $(JC1FLAGS)
$(LDFLAGS) -o $@
-LIBLINK = $(LIBTOOL) --tag=CXX --mode=link $(CXX) -L$(here) $(JC1FLAGS)
$(LDFLAGS) -o $@
+GCJCOMPILE = $(LIBTOOL) --mode=compile $(GCJ_WITH_FLAGS) -fclasspath=
-fbootclasspath=$(here) $(JC1FLAGS) -MD -MT $@ -MF $(@:.lo=.d) -c
+GCJLINK = $(LIBTOOL) --mode=link $(GCJ) -L$(here) $(JC1FLAGS) $(LDFLAGS) -o $@
+LIBLINK = $(LIBTOOL) --mode=link $(CXX) -L$(here) $(JC1FLAGS) $(LDFLAGS) -o $@
## We define this because otherwise libtool can be run with different
## values of `CXX' and will then get confused and fail to work. So,
## we use --tag explicitly. Someday automake will be changed to do
## this automatically.
-LTCXXCOMPILE = $(LIBTOOL) --tag=CXX --mode=compile $(CXX) $(DEFS) $(INCLUDES)
$(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS)
+LTCXXCOMPILE = $(LIBTOOL) --mode=compile $(CXX) $(DEFS) $(INCLUDES)
$(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS)
JAVAC = $(GCJ_WITH_FLAGS) -C
--- libstdc++-v3/testsuite/Makefile.am 2002-09-05 22:20:47.0 -0700
+++ libstdc++-v3/testsuite/Makefile.am 2003-01-22 05:14:50.0 -0800
@@ -41,7 +41,7 @@
CXX=`echo $(CXX_fake) | sed 's/xgcc/g++/g'`
CXXLINK = \
LD_RUN_PATH=${LD_RUN_PATH:+$LD_RUN_PATH:}${glibcpp_builddir}/src/.libs\
- $(LIBTOOL) --tag=
Bug#176311: gcc-3.2: configure generated from broken libtool.m4
On Fri, Jan 24, 2003 at 08:57:08AM +0100, Matthias Klose wrote:
> Benjamin Kosnik writes:
> > On Sun, 12 Jan 2003 11:25:04 +0100
> > Matthias Klose <[EMAIL PROTECTED]> wrote:
> >
> > >Is it likely this will be addressed in the gcc-3.2 branch?
> >
> > Are you volunteering?
>
> Ryan Murray provided a patch, which I attach here. Needed for the 3.3
> branch as well. checked on mips{,el}-linux and i386-linux only.
>
> The patch touches a few Makefile.am's to remove the
> --tag option to libtool (doesn't exist), and then uses autoreconf on the
> subdirs, and copies in things to the top level.
> gnu automake)
>
> After applying the patch:
>
> libtoolize --force --copy
> cp /usr/share/aclocal/libtool.m4 . # (from libtool-1.4.3)
> for i in libf2c libjava/libltdl libobjc libstdc++-v3 zlib; do
> (cd ${i} ; autoreconf --force)
> done
Note that this will render the other libtool using subdirectories as
broken until someone fixes up the automake/autoconf in that directory.
Specifically, libjava, libffi, and boehm-gc will need to have Makefile.am
updated to work with the version of automake in use (1.4), and then those
directories will also have to be autoreconf'd
--
Ryan Murray, Debian Developer ([EMAIL PROTECTED], [EMAIL PROTECTED])
The opinions expressed here are my own.
pgpeAIribnrxq.pgp
Description: PGP signature
Re: Gcc 3.x seems to create incorrect code
Miah Gregory <[EMAIL PROTECTED]> writes: > As such, I've come here in the hope that someone can suggest how I might > find out the exact cause of the problem, as I've never had to try and track > down potential compiler bugs before. Dear Miah, As a starting point, you have to find precisely out what goes wrong. If the compiler emits bad code, it is as if you had written an incorrect algorithm yourself. The problem is typically confined to a single location, such as an if statement that is not executed although it should. So you have to trace through the code and look for the first place where it misbehaves. This would be best done in a debugger, but if that is not possible, you have add print statements to see how it traces through the code. Then you will find where the camera should have been recognized but isn't. Try to narrow the incorrect statement down as much as possible. Pointing to the precise function that is miscompiled is required, pointing to the precise statement or expression would be good. Then look at the assembler output; compile this specific translation unit with -save-temps. If you know assembler, see how the assembler matches your source code, and find the place where it doesn't match, then submit a bug report. If you don't know assembler, submit a bug report right away, including both the preprocessor output and the assembler file. We are certainly interested to eliminate all compiler bugs that cause kernel miscompilation. Please understand, though, that you don't *necessarily* have encountered a compiler bug: It may be that you rely on undefined or unspecified behaviour in your code, and that gcc 3.2 choses to interpret your code differently than 2.95. In this case, you need to correct your code, to only use well-defined constructs. HTH, Martin
Results for 3.2.1 20020924 (Debian prerelease) testsuite on m68k-unknown-linux-gnu
LAST_UPDATED: Tue Sep 24 07:36:40 UTC 2002 Native configuration is m68k-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.eh/spec3.C Execution test FAIL: g++.eh/spec4.C Execution test FAIL: g++.robertl/eb83.C Execution test === g++ Summary === # of expected passes7246 # of unexpected failures3 # of expected failures 88 # of untested testcases 23 # of unsupported tests 6 /build/younie/gcc-3.2-3.2.1ds2/build/gcc/testsuite/../g++ version 3.2.1 20020924 (Debian prerelease) === g77 tests === Running target unix FAIL: g77.dg/bprob/bprob-1.f execution,-g -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -g -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-g -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-O0 -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -O0 -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-O0 -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-O1 -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -O1 -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-O1 -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-O2 -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -O2 -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-O2 -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-O3 -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -O3 -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-O3 -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-O3 -g -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -O3 -g -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-O3 -g -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-Os -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -Os -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-Os -fbranch-probabilities FAIL: g77.dg/gcov/gcov-1.f execution test FAIL: g77.dg/gcov/gcov-1.f gcov: 118 failures in line counts, 32 in branch percentages, 24 in return percentages FAIL: g77.f-torture/execute/20010430.f execution, -O2 FAIL: g77.f-torture/execute/20010430.f execution, -O3 -fomit-frame-pointer FAIL: g77.f-torture/execute/20010430.f execution, -O3 -fomit-frame-pointer -funroll-loops FAIL: g77.f-torture/execute/20010430.f execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions FAIL: g77.f-torture/execute/20010430.f execution, -O3 -g WARNING: program timed out. FAIL: g77.f-torture/execute/intrinsic77.f compilation, -O3 -fomit-frame-pointer WARNING: program timed out. FAIL: g77.f-torture/execute/intrinsic77.f compilation, -O3 -g === g77 Summary === # of expected passes1420 # of unexpected failures16 # of unresolved testcases 14 # of untested testcases 2 # of unsupported tests 8 /build/younie/gcc-3.2-3.2.1ds2/build/gcc/testsuite/../g77 version 3.2.1 20020924 (Debian prerelease) === gcc tests === Running target unix WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O0 WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O1 WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O2 WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -fomit-frame-pointer WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -g WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -Os FAIL: gcc.c-torture/execute/20010122-1.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/20010122-1.c execution, -O3 -fomit-frame-pointer -funroll-loops FAIL: gcc.c-torture/execute/20010122-1.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions FAIL: gcc.c-torture/execute/20020418-1.c execution, -O2 FAIL: gcc.c-torture/execute/20020418-1.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/20020418-1.c execution, -O3 -g FAIL: gcc.c-torture/execute/20020418-1.c execution, -Os FAIL: gcc.c-torture/execute/loop-2e.c execution, -O0 FAIL: gcc.c-torture/execute/loop-2e.c execution, -O1 FAIL: gcc.c-torture/execute/loop-2e.c execution, -O2 FAIL: gcc.c-torture/execute/loop-2e.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/loop-2e.c execution, -O3 -fomit-frame-pointer -funroll-loops FAIL: gcc.c-torture/execute/loop-2e.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions FAIL: gcc.c-torture/execute/loop-2e.c execution, -O3 -g FAIL: gcc.c-torture/execute/loop-2e.c execution, -Os FAIL: gcc.c-torture/execute/loop-2f.c execution, -O0 FAIL: gcc.c-torture/execute/loop-2f.c execution, -O1 FA
Results for 3.2.2 20021231 (Debian prerelease) testsuite on m68k-unknown-linux-gnu
LAST_UPDATED: Tue Dec 31 12:49:32 UTC 2002 Native configuration is m68k-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.eh/spec3.C Execution test FAIL: g++.eh/spec4.C Execution test WARNING: program timed out. FAIL: g++.law/virtual3.C (test for excess errors) FAIL: g++.law/virtual3.C Execution test WARNING: program timed out. FAIL: g++.other/headers1.C (test for excess errors) FAIL: g++.other/headers1.C Execution test XPASS: g++.other/init5.C Execution test FAIL: g++.robertl/eb83.C Execution test === g++ Summary === # of expected passes7326 # of unexpected failures7 # of unexpected successes 1 # of expected failures 88 # of untested testcases 23 # of unsupported tests 6 /home/gotom/gcc/gcc-3.2-3.2.2ds3/build/gcc/testsuite/../g++ version 3.2.2 20021231 (Debian prerelease) === g77 tests === Running target unix FAIL: g77.dg/bprob/bprob-1.f execution,-g -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -g -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-g -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-O0 -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -O0 -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-O0 -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-O1 -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -O1 -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-O1 -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-O2 -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -O2 -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-O2 -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-O3 -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -O3 -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-O3 -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-O3 -g -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -O3 -g -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-O3 -g -fbranch-probabilities FAIL: g77.dg/bprob/bprob-1.f execution,-Os -fprofile-arcs UNRESOLVED: g77.dg/bprob/bprob-1.f compilation, -Os -fbranch-probabilities UNRESOLVED: g77.dg/bprob/bprob-1.f execution,-Os -fbranch-probabilities FAIL: g77.dg/gcov/gcov-1.f execution test FAIL: g77.dg/gcov/gcov-1.f gcov: 118 failures in line counts, 32 in branch percentages, 24 in return percentages FAIL: g77.f-torture/execute/20010430.f execution, -O2 FAIL: g77.f-torture/execute/20010430.f execution, -O3 -fomit-frame-pointer FAIL: g77.f-torture/execute/20010430.f execution, -O3 -fomit-frame-pointer -funroll-loops FAIL: g77.f-torture/execute/20010430.f execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions FAIL: g77.f-torture/execute/20010430.f execution, -O3 -g WARNING: program timed out. FAIL: g77.f-torture/execute/f90-intrinsic-bit.f compilation, -Os WARNING: program timed out. FAIL: g77.f-torture/execute/intrinsic77.f compilation, -O3 -fomit-frame-pointer WARNING: program timed out. FAIL: g77.f-torture/execute/intrinsic77.f compilation, -O3 -g === g77 Summary === # of expected passes1418 # of unexpected failures17 # of unresolved testcases 14 # of untested testcases 3 # of unsupported tests 8 /home/gotom/gcc/gcc-3.2-3.2.2ds3/build/gcc/testsuite/../g77 version 3.2.2 20021231 (Debian prerelease) === gcc tests === Running target unix WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O0 WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O1 WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O2 WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -fomit-frame-pointer WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -g WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -Os FAIL: gcc.c-torture/execute/20010122-1.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/20010122-1.c execution, -O3 -fomit-frame-pointer -funroll-loops FAIL: gcc.c-torture/execute/20010122-1.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions WARNING: program timed out. FAIL: gcc.c-torture/execute/20020108-1.c compilation, -Os UNRESOLVED: gcc.c-torture/execute/20020108-1.c execution, -Os FAIL: gcc.c-torture/execute/20020418-1.c execution, -O2 FAIL: gcc.c-torture/execute/20020418-1.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/20020418-1.c execution, -O3 -g FAIL: gcc.c-torture/execute/20020418-1.c execution, -Os FAIL: gcc.c-torture/execute/loop-2e.c execution, -O0 FAIL: gcc.c-torture/execute/loop-2e.c execution,
gcc-3.2 override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): g++-3.2_3.2.2-0pre6_i386.deb: package says priority is optional, override says standard. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED])
gcc-3.2_3.2.2ds5-0pre6_i386.changes ACCEPTED
Accepted: cpp-3.2-doc_3.2.2-0pre6_all.deb to pool/main/g/gcc-3.2/cpp-3.2-doc_3.2.2-0pre6_all.deb cpp-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/cpp-3.2_3.2.2-0pre6_i386.deb fastjar_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/fastjar_3.2.2-0pre6_i386.deb fixincludes_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/fixincludes_3.2.2-0pre6_i386.deb g++-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/g++-3.2_3.2.2-0pre6_i386.deb g77-3.2-doc_3.2.2-0pre6_all.deb to pool/main/g/gcc-3.2/g77-3.2-doc_3.2.2-0pre6_all.deb g77-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/g77-3.2_3.2.2-0pre6_i386.deb gcc-3.2-base_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/gcc-3.2-base_3.2.2-0pre6_i386.deb gcc-3.2-doc_3.2.2-0pre6_all.deb to pool/main/g/gcc-3.2/gcc-3.2-doc_3.2.2-0pre6_all.deb gcc-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/gcc-3.2_3.2.2-0pre6_i386.deb gcc-3.2_3.2.2ds5-0pre6.diff.gz to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds5-0pre6.diff.gz gcc-3.2_3.2.2ds5-0pre6.dsc to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds5-0pre6.dsc gcc-3.2_3.2.2ds5.orig.tar.gz to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds5.orig.tar.gz gcj-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/gcj-3.2_3.2.2-0pre6_i386.deb gij-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/gij-3.2_3.2.2-0pre6_i386.deb gnat-3.2-doc_3.2.2-0pre6_all.deb to pool/main/g/gcc-3.2/gnat-3.2-doc_3.2.2-0pre6_all.deb gnat-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/gnat-3.2_3.2.2-0pre6_i386.deb gobjc-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/gobjc-3.2_3.2.2-0pre6_i386.deb gpc-2.1-3.2-doc_3.2.2.20021128-0pre6_all.deb to pool/main/g/gcc-3.2/gpc-2.1-3.2-doc_3.2.2.20021128-0pre6_all.deb gpc-2.1-3.2_3.2.2.20021128-0pre6_i386.deb to pool/main/g/gcc-3.2/gpc-2.1-3.2_3.2.2.20021128-0pre6_i386.deb libffi2-dev_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libffi2-dev_3.2.2-0pre6_i386.deb libffi2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libffi2_3.2.2-0pre6_i386.deb libg2c0_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libg2c0_3.2.2-0pre6_i386.deb libgcc1_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libgcc1_3.2.2-0pre6_i386.deb libgcj-common_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libgcj-common_3.2.2-0pre6_i386.deb libgcj3-dev_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libgcj3-dev_3.2.2-0pre6_i386.deb libgcj3_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libgcj3_3.2.2-0pre6_i386.deb libgnat3.15a_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libgnat3.15a_3.2.2-0pre6_i386.deb libobjc1_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libobjc1_3.2.2-0pre6_i386.deb libstdc++5-dbg_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libstdc++5-dbg_3.2.2-0pre6_i386.deb libstdc++5-dev_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libstdc++5-dev_3.2.2-0pre6_i386.deb libstdc++5-doc_3.2.2-0pre6_all.deb to pool/main/g/gcc-3.2/libstdc++5-doc_3.2.2-0pre6_all.deb libstdc++5-pic_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libstdc++5-pic_3.2.2-0pre6_i386.deb libstdc++5_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/libstdc++5_3.2.2-0pre6_i386.deb protoize_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/protoize_3.2.2-0pre6_i386.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 176311 177674 177679 Thank you for your contribution to Debian.
Bug#177674: marked as done (Outdated config.sub/config.guess)
Your message dated Fri, 24 Jan 2003 06:17:43 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#177674: fixed in gcc-3.2 1:3.2.2ds5-0pre6
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
Received: (at submit) by bugs.debian.org; 21 Jan 2003 05:47:15 +
>From [EMAIL PROTECTED] Mon Jan 20 23:47:14 2003
Return-path: <[EMAIL PROTECTED]>
Received: from 34.mufa.clsp.snfccafj.dsl.att.net (dogma.lightbearer.com)
[12.99.69.34] (qmailr)
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 18arFi-0007Bj-00; Mon, 20 Jan 2003 23:47:14 -0600
Received: (qmail 26950 invoked by uid 1000); 21 Jan 2003 05:47:12 -
Date: Mon, 20 Jan 2003 22:47:12 -0700
From: Joel Baker <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Outdated config.sub/config.guess
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz"
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-6.4 required=5.0
tests=PGP_SIGNATURE_2,SPAM_PHRASE_00_01,USER_AGENT,
USER_AGENT_MUTT
version=2.41
X-Spam-Level:
--3V7upXqbjpZ4EhLz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Package: gcc-3.2
Version: 3.2.2ds4
Severity: wishlist
The config.{sub,guess} scripts in the source tarball are not up to date,
and as such, do not correctly handle the recently added config triplet for
Debian NetBSD/i386 systems (i386-unknown-netbsdelf-gnu). These scripts
occur in the root source directory, as well as the boehm-gc subdirectory.
Updated config scripts can be found in the upstream CVS as of 2002-11-30, or
the autotools-dev package, version 20021130.1.
--=20
Joel Baker <[EMAIL PROTECTED]>
--3V7upXqbjpZ4EhLz
Content-Type: application/pgp-signature
Content-Disposition: inline
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE+LN7glZCPwGNtWe4RAlr4AJ9sQK3wjg+7C9jVwwTz5al+9qTZ5gCghGg7
4EicPc6LGGxg1NqEYjQKRnA=
=p8FU
-END PGP SIGNATURE-
--3V7upXqbjpZ4EhLz--
---
Received: (at 177674-close) by bugs.debian.org; 24 Jan 2003 11:23:13 +
>From [EMAIL PROTECTED] Fri Jan 24 05:23:13 2003
Return-path: <[EMAIL PROTECTED]>
Received: from auric.debian.org [206.246.226.45] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18c1vV-00089O-00; Fri, 24 Jan 2003 05:23:13 -0600
Received: from katie by auric.debian.org with local (Exim 3.35 1 (Debian))
id 18c1qB-00037M-00; Fri, 24 Jan 2003 06:17:43 -0500
From: Matthias Klose <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.29 $
Subject: Bug#177674: fixed in gcc-3.2 1:3.2.2ds5-0pre6
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 24 Jan 2003 06:17:43 -0500
Delivered-To: [EMAIL PROTECTED]
We believe that the bug you reported is fixed in the latest version of
gcc-3.2, which is due to be installed in the Debian FTP archive:
cpp-3.2-doc_3.2.2-0pre6_all.deb
to pool/main/g/gcc-3.2/cpp-3.2-doc_3.2.2-0pre6_all.deb
cpp-3.2_3.2.2-0pre6_i386.deb
to pool/main/g/gcc-3.2/cpp-3.2_3.2.2-0pre6_i386.deb
fastjar_3.2.2-0pre6_i386.deb
to pool/main/g/gcc-3.2/fastjar_3.2.2-0pre6_i386.deb
fixincludes_3.2.2-0pre6_i386.deb
to pool/main/g/gcc-3.2/fixincludes_3.2.2-0pre6_i386.deb
g++-3.2_3.2.2-0pre6_i386.deb
to pool/main/g/gcc-3.2/g++-3.2_3.2.2-0pre6_i386.deb
g77-3.2-doc_3.2.2-0pre6_all.deb
to pool/main/g/gcc-3.2/g77-3.2-doc_3.2.2-0pre6_all.deb
g77-3.2_3.2.2-0pre6_i386.deb
to pool/main/g/gcc-3.2/g77-3.2_3.2.2-0pre6_i386.deb
gcc-3.2-base_3.2.2-0pre6_i386.deb
to pool/main/g/gcc-3.2/gcc-3.2-base_3.2.2-0pre6_i386.deb
gcc-3.2-doc_3.2.2-0pre6_all.deb
to pool/main/g/gcc-3.2/gcc-3.2-doc_3.2.2-0pre6_all.deb
gcc-3.2_3.2.2-0pre6_i386.deb
to pool/main/g/gcc-3.2/gcc-3.2_3.2.2-0pre6_i386.deb
gcc-3.2_3.2.2ds5-0pre6.diff.gz
to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds5-0pre6.diff.gz
gcc-3.2_3.2.2ds5-0pre6.dsc
to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds5-0pre6.dsc
gcc-3.2_3.2.2ds5.orig.tar.gz
to pool/main/g/gcc-3.2/gcc-3.2_3.2.2ds5.orig.tar.gz
gcj-3.2_3.2.2-0pre6_i386.deb
to pool/main/g/gcc-3.2/gcj-3.2_3.2.2-0pre6_i386.deb
gij-3.2_3.2.2-0pre6_i386.deb
to pool/main/g/gcc-3.2/gij-3.2_3.2.2-0pre6_i386.deb
gnat-3.2-doc_3.2.2-0pre6_all.deb
to pool/main/g/gcc-3.2/gnat-3.2-doc_3.
Bug#176311: marked as done (gcc-3.2: configure generated from broken libtool.m4)
Your message dated Fri, 24 Jan 2003 06:17:43 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#176311: fixed in gcc-3.2 1:3.2.2ds5-0pre6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 11 Jan 2003 22:18:56 + >From [EMAIL PROTECTED] Sat Jan 11 16:18:55 2003 Return-path: <[EMAIL PROTECTED]> Received: from (straylight.cyberhqz.com) [24.77.96.253] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 18XTxv-0003K5-00; Sat, 11 Jan 2003 16:18:55 -0600 Received: by straylight.cyberhqz.com (Postfix, from userid 1000) id 34AE75404A; Sat, 11 Jan 2003 14:18:54 -0800 (PST) From: Ryan Murray <[EMAIL PROTECTED]> Subject: gcc-3.2: configure generated from broken libtool.m4 To: [EMAIL PROTECTED] X-Mailer: bug 3.3.10.1 Message-Id: <[EMAIL PROTECTED]> Date: Sat, 11 Jan 2003 14:18:54 -0800 (PST) Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=0.1 required=5.0 tests=SPAM_PHRASE_03_05 version=2.41 X-Spam-Level: Package: gcc-3.2 Version: 1:3.2.2ds4-0pre5 Severity: grave The version of libtool used to build this source package is too old to correctly support shared libraries for the Debian mips and mipsel architectures. At least version (1.4.2-7) and higher correctly supports them. You need to update all of the libtool related files by running the following on your source tree: libtoolize --force --copy aclocal autoheader automake autoconf autoheader may not be needed, and you may need to use autoconf2.13 rather than autoconf. You may also need to apply the patch in libtool bug #98342 if your package builds more than one library, where one library depends on the other. Versions of libtool from 1.4.2-7.1 include a fix for this problem already, so using the newest version is recommended. The correct 'configure' script will have output that looks like this: # This must be Linux ELF. linux-gnu*) case $host_cpu in alpha* | hppa* | i*86 | mips | mipsel | powerpc* | sparc* | ia64* | s390* ) lt_cv_deplibs_check_method=pass_all ;; *) Older versions of libtool used a file_magic check for the pattern file_magic ELF [0-9][0-9]*-bit [LM]SB (shared object|dynamic lib ) The output of file(1) on a shared library on MIPS does not match this regular expression, however. Earlier versions of file had been modified to match this regular expression, but the latest version uses the same output as upstream once again. The file check often causes problems, and results on a build-dep on file that you might not otherwise be aware of. The new method doesn't need file(1) at all, and is far less fragile, so it is best to upgrade the configure script with proper mips support. This problem causes libstdc++ to be built improperly, without depending on shared libraries that it needs to, which in turn breaks several other c++ builds. --- Received: (at 176311-close) by bugs.debian.org; 24 Jan 2003 11:23:14 + >From [EMAIL PROTECTED] Fri Jan 24 05:23:14 2003 Return-path: <[EMAIL PROTECTED]> Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 18c1vV-00089W-00; Fri, 24 Jan 2003 05:23:13 -0600 Received: from katie by auric.debian.org with local (Exim 3.35 1 (Debian)) id 18c1qB-00037K-00; Fri, 24 Jan 2003 06:17:43 -0500 From: Matthias Klose <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.29 $ Subject: Bug#176311: fixed in gcc-3.2 1:3.2.2ds5-0pre6 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Fri, 24 Jan 2003 06:17:43 -0500 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is fixed in the latest version of gcc-3.2, which is due to be installed in the Debian FTP archive: cpp-3.2-doc_3.2.2-0pre6_all.deb to pool/main/g/gcc-3.2/cpp-3.2-doc_3.2.2-0pre6_all.deb cpp-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/cpp-3.2_3.2.2-0pre6_i386.deb fastjar_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/fastjar_3.2.2-0pre6_i386.deb fixincludes_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/fixincludes_3.2.2-0pre6_i386.deb g++-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/g++-3.2_3.2.2-0pre6_i386.deb g77-3.2-doc_3.2.2-0pre6_all.deb to pool/main/g/gcc-3.2/g77-3.2-doc_3.2.2-0pre6_all.deb g77-3.2_3.2.2-0pre6_i386.deb to pool/main/g/gcc-3.2/g77-3.2_3.2.2-0pre6_i386.deb gcc-3.2-base_3.2.2-0pre6_i386.deb
Bug#177679: marked as done (NetBSD/i386 does not successfully build Ada or Java)
Your message dated Fri, 24 Jan 2003 06:17:43 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#177679: fixed in gcc-3.2 1:3.2.2ds5-0pre6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 21 Jan 2003 06:17:12 + >From [EMAIL PROTECTED] Tue Jan 21 00:17:12 2003 Return-path: <[EMAIL PROTECTED]> Received: from 34.mufa.clsp.snfccafj.dsl.att.net (dogma.lightbearer.com) [12.99.69.34] (qmailr) by master.debian.org with smtp (Exim 3.12 1 (Debian)) id 18arig-dj-00; Tue, 21 Jan 2003 00:17:11 -0600 Received: (qmail 27859 invoked by uid 1000); 21 Jan 2003 06:17:04 - From: "Joel Baker" <[EMAIL PROTECTED]> Date: Mon, 20 Jan 2003 23:17:04 -0700 To: [EMAIL PROTECTED] Subject: NetBSD/i386 does not successfully build Ada or Java Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="24zk1gE8NUlDmwG9" Content-Disposition: inline User-Agent: Mutt/1.3.28i Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-6.4 required=5.0 tests=PGP_SIGNATURE_2,SPAM_PHRASE_00_01,USER_AGENT, USER_AGENT_MUTT version=2.41 X-Spam-Level: --24zk1gE8NUlDmwG9 Content-Type: multipart/mixed; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: gcc-3.2 Version: 3.2.2ds4 Severity: wishlist Tags: patch The NetBSD/i386 port does not currently cope well with building Ada or Java; as such, I would request that the attached patches be accepted until such time as we can get things to pass the test suites and work in some sane fashion. --=20 Joel Baker <[EMAIL PROTECTED]> --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=002_no_gnat diff -urN debian.orig/rules.defs debian/rules.defs --- debian.orig/rules.defs Wed Sep 4 16:48:17 2002 +++ debian/rules.defs Wed Sep 4 16:50:36 2002 @@ -235,7 +235,7 @@ # Ada with_ada := yes with_shared_adalib := no -ada_no_archs := arm hurd-i386 m68k freebsd-i386 +ada_no_archs := arm hurd-i386 m68k freebsd-i386 netbsd-i386 ifneq ($(DEB_HOST_ARCH),i386) ifeq ($(DEB_HOST_ARCH), $(findstring $(DEB_HOST_ARCH),$(ada_no_archs))) with_ada := disabled for architecure $(DEB_HOST_ARCH) --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=003_no_java Content-Transfer-Encoding: quoted-printable --- debian/rules.defs.orig 2003-01-21 05:56:17.0 + +++ debian/rules.defs 2003-01-21 05:56:46.0 + @@ -126,7 +126,7 @@ # Build all packages needed for Java development (gcj, libgcj-dev) with_javadev :=3D yes =20 -no_java_archs :=3D hppa hurd-i386 mips mipsel freebsd-i386 +no_java_archs :=3D hppa hurd-i386 mips mipsel freebsd-i386 netbsd-i386 ifneq ($(DEB_HOST_ARCH),i386) ifeq ($(DEB_HOST_ARCH), $(findstring $(DEB_HOST_ARCH),$(no_java_archs))) with_java :=3D disabled for architecure $(DEB_HOST_ARCH) @@ -149,7 +149,7 @@ # libffi --- ifeq ($(with_common_pkgs),yes) with_ffi :=3D yes - no_ffi_archs :=3D hppa mips mipsel hurd-i386 freebsd-i386 + no_ffi_archs :=3D hppa mips mipsel hurd-i386 freebsd-i386 netbsd-i386 ifneq ($(with_java),yes) ifeq ($(DEB_HOST_ARCH), $(findstring $(DEB_HOST_ARCH),$(no_ffi_archs))) with_ffi :=3D disabled for architecure $(DEB_HOST_ARCH) --h31gzZEtNLTqOjlF-- --24zk1gE8NUlDmwG9 Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+LOXglZCPwGNtWe4RAhEbAJ9b5rOqOurpretRal5yk814A+GPUQCgiMoi 2IuVlOf3CADnbPIpA7os0oc= =tZkV -END PGP SIGNATURE- --24zk1gE8NUlDmwG9-- --- Received: (at 177679-close) by bugs.debian.org; 24 Jan 2003 11:27:52 + >From [EMAIL PROTECTED] Fri Jan 24 05:27:52 2003 Return-path: <[EMAIL PROTECTED]> Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 18c1zz-0008Ss-00; Fri, 24 Jan 2003 05:27:51 -0600 Received: from katie by auric.debian.org with local (Exim 3.35 1 (Debian)) id 18c1qB-00037O-00; Fri, 24 Jan 2003 06:17:43 -0500 From: Matthias Klose <[EMAIL PROTECTED]> To: [EMAIL PROTECTE
Bug#176311: gcc-3.2: configure generated from broken libtool.m4
At 08:57 24.01.2003, Matthias Klose wrote:
Benjamin Kosnik writes:
> On Sun, 12 Jan 2003 11:25:04 +0100
> Matthias Klose <[EMAIL PROTECTED]> wrote:
>
> >Is it likely this will be addressed in the gcc-3.2 branch?
>
> Are you volunteering?
Ryan Murray provided a patch, which I attach here. Needed for the 3.3
branch as well. checked on mips{,el}-linux and i386-linux only.
The patch touches a few Makefile.am's to remove the
--tag option to libtool (doesn't exist), and then uses autoreconf on the
subdirs, and copies in things to the top level.
gnu automake)
The --tag option doesn't exist in your libtool simply because the one used
in gcc is from a different libtool branch. Simply don't touch these files
unless you know exactly what you are doing with this _extremely_ fragile
stuff. This is certainly no task for 3.2 or 3.3, and Nathaneal already
works on the mainline.
Franz.
Bug#176311: gcc-3.2: configure generated from broken libtool.m4
>Note that this will render the other libtool using subdirectories as >broken until someone fixes up the automake/autoconf in that directory. > >Specifically, libjava, libffi, and boehm-gc will need to have Makefile.am >updated to work with the version of automake in use (1.4), and then those >directories will also have to be autoreconf'd I don't think this is going to fly. I think you'll get more traction if you do this on a per-directory basis: libstdc++-v3, libjava, etc all separated out. Also, please pick a gcc list to cc, not three. -benjamin
Bug#176311: gcc-3.2: configure generated from broken libtool.m4
On Jan 24, 2003, Matthias Klose <[EMAIL PROTECTED]> wrote: > The patch touches a few Makefile.am's to remove the > --tag option to libtool (doesn't exist), It does exist in the libtool.m4 that's in the top level of the hierarchy, and that's what you're supposed to use. Not using it, and removing --tag, means you'll be dropping multi-language support, that's the very reason why GCC uses this particular version of libtool, that is conceptually newer than the latest release of libtool out of its 1.4 branch. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer [EMAIL PROTECTED], gcc.gnu.org} CS PhD student at IC-Unicamp[EMAIL PROTECTED], gnu.org} Free Software EvangelistProfessional serial bug killer
Bug#176311: gcc-3.2: configure generated from broken libtool.m4
On Fri, Jan 24, 2003 at 05:27:45PM +0100, Franz Sirl wrote:
> >Ryan Murray provided a patch, which I attach here. Needed for the 3.3
> >branch as well. checked on mips{,el}-linux and i386-linux only.
> >
> >The patch touches a few Makefile.am's to remove the
> >--tag option to libtool (doesn't exist), and then uses autoreconf on the
> >subdirs, and copies in things to the top level.
> >gnu automake)
>
> The --tag option doesn't exist in your libtool simply because the one used
> in gcc is from a different libtool branch. Simply don't touch these files
The branch of libtool that supports --tag has been totally untouched
in cvs for at least two years. It doesn't work for mips{,el}-linux
> unless you know exactly what you are doing with this _extremely_ fragile
> stuff. This is certainly no task for 3.2 or 3.3, and Nathaneal already
> works on the mainline.
I'm aware that it's exteremely fragile, and the effects it has.
However, gcc 3.2/3.3 doesn't build properly on Linux/mips{,el} without
doing something to address this. Specifically, libstdc++ and libf2c don't
have their dependencies specified at linktime, because libtool can't figure
out that there are shared libraries available. If people think fixing the
unmaintained libtool is a better option for 3.2/3.3, I can look at that
instead.
--
Ryan Murray, Debian Developer ([EMAIL PROTECTED], [EMAIL PROTECTED])
The opinions expressed here are my own.
pgpdUPofPkuYL.pgp
Description: PGP signature
Bug#176311: gcc-3.2: configure generated from broken libtool.m4
On Fri, Jan 24, 2003 at 10:06:31AM -0600, Benjamin Kosnik wrote: > >Specifically, libjava, libffi, and boehm-gc will need to have Makefile.am > >updated to work with the version of automake in use (1.4), and then those > >directories will also have to be autoreconf'd > > I think you'll get more traction if you do this on a per-directory > basis: libstdc++-v3, libjava, etc all separated out. Not possible. Everything uses the top level libtool.m4. They either all match, or it's not going to build. -- Ryan Murray, Debian Developer ([EMAIL PROTECTED], [EMAIL PROTECTED]) The opinions expressed here are my own. pgplCQmujvrVb.pgp Description: PGP signature
Bug#176311: gcc-3.2: configure generated from broken libtool.m4
[EMAIL PROTECTED] (Ryan Murray) writes: |> The branch of libtool that supports --tag has been totally untouched |> in cvs for at least two years. The multi-language-branch is dead, and has been merged into HEAD nearly two years ago. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Bug#176311: gcc-3.2: configure generated from broken libtool.m4
On Fri, Jan 24, 2003 at 10:08:36PM +0100, Andreas Schwab wrote: > [EMAIL PROTECTED] (Ryan Murray) writes: > > |> The branch of libtool that supports --tag has been totally untouched > |> in cvs for at least two years. > > The multi-language-branch is dead, and has been merged into HEAD nearly > two years ago. Ahh, I missed the fact that it was actually still present in HEAD. So we can either relibtoolize with a libtool built from CVS HEAD, or patch the existing libtool.m4 in 3.2/3.3 to work. I'm guessing it would be preferred not to relibtoolize 3.2/3.3, but just to fix what is there? -- Ryan Murray, Debian Developer ([EMAIL PROTECTED], [EMAIL PROTECTED]) The opinions expressed here are my own. pgpnjzoOTDOY3.pgp Description: PGP signature
Re: Bug #175526
On Fri, Jan 24, 2003 at 11:34:34AM +0900, GOTO Masanori wrote: > > which binutils are used? Some older versions had bugs that were > > only triggered by gcc-3.2 > > At least I tested with binutils 2.13.90.0.16-1. > But, I don't know the version number of the buildd environment. seems to be the version used during the build as well. Haven't tested this version but the problems I mentioned were much older.. lets see what the new build does. Richard
Re: Bug#175526: Bug #175526
On Fri, Jan 24, 2003 at 10:23:01PM +0100, Richard Zidlicky wrote: > > At least I tested with binutils 2.13.90.0.16-1. > > But, I don't know the version number of the buildd environment. > seems to be the version used during the build as well. Haven't > tested this version but the problems I mentioned were much older.. > lets see what the new build does. I don't know if it's significant, but upstream announced .18 today with the following changelog: Changes from binutils 2.13.90.0.16: 1. Update from binutils 2003 0121. 2. Fix an ia64 gas bug. 3. Fix some TLS bugs. 4. Fix some ELF/ppc bugs. 5. Fix an ELF/m68k bug. Tks, Jeff Bailey
Bug#178284: gcc-3.2: info gcc does not display gcc manual
Package: gcc-3.2 Version: 1:3.2.2-0pre6 Severity: minor info gcc gives me the gccint-3.2.info file, but it would be more logical to present gcc-3.2.info. man gcc works as expected. -- System Information Debian Release: testing/unstable Kernel Version: Linux endquote 2.5.53 #2 Mon Dec 30 16:36:48 PST 2002 i686 unknown unknown GNU/Linux Versions of the packages gcc-3.2 depends on: ii binutils 2.13.90.0.16-1 The GNU assembler, linker and binary utiliti ii cpp-3.23.2.2-0pre6The GNU C preprocessor ii gcc-3.2-base 3.2.2-0pre6The GNU Compiler Collection (base package) ii libc6 2.3.1-10 GNU C Library: Shared libraries and Timezone ii libgcc13.2.2-0pre6GCC support library
Processed: Minor problem...
Processing commands for [EMAIL PROTECTED]: > reopen 177674 Bug#177674: Outdated config.sub/config.guess Bug reopened, originator not changed. > retitle 177674 Missing Build-Depends on autotools-dev Bug#177674: Outdated config.sub/config.guess Changed Bug title. > severity 177674 minor Bug#177674: Missing Build-Depends on autotools-dev Severity set to `minor'. > Packages which directly access the scripts from autotools-dev (such as Unknown command or malformed arguments to command. > the cp -p command placed into GCC in the last version) need to declare a Unknown command or malformed arguments to command. > Build-Depend on the autotools-dev package. Unknown command or malformed arguments to command. > Thank you for making the update; this is just a minor follow-up. Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#177674: Minor problem...
reopen 177674 retitle 177674 Missing Build-Depends on autotools-dev severity 177674 minor Packages which directly access the scripts from autotools-dev (such as the cp -p command placed into GCC in the last version) need to declare a Build-Depend on the autotools-dev package. Thank you for making the update; this is just a minor follow-up. -- Joel Baker <[EMAIL PROTECTED]> pgpEeq33o1RJD.pgp Description: PGP signature
