gcc-4.0: ftbfs [sparc] make[2]: *** No rule to make target `current_symbols.txt'

Bug #22541 reported by Debian Bug Importer
6
Affects Status Importance Assigned to Milestone
gcc-4.0 (Debian)
Fix Released
Unknown
gcc-4.0 (Ubuntu)
Invalid
High
Matthias Klose

Bug Description

Automatically imported from Debian bug report #330101 http://bugs.debian.org/330101

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #330101 http://bugs.debian.org/330101

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 25 Sep 2005 16:38:04 -0700
From: Blars Blarson <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: gcc-4.0: ftbfs [sparc] make[2]: *** No rule to make target `current_symbols.txt'

Package: gcc-4.0
Version: 4.0.1-9
Severity: serious
Justification: fails to build from source

gcc-4.0 failed to build on a sparc buildd, but succeeded on my sparc
pbuilder. Possible reasons for this include timestamp scew, more
recent kernel version on my pbuilder, and more recent
build-dependancies.

cat debian/README.libstdc++-baseline.in \
 > debian/README.libstdc++-baseline
baseline_name=`basename /build/buildd/gcc-4.0-4.0.1/src/libstdc++-v3/config/abi/sparc-linux-gnu`; \
baseline_parentdir=`dirname /build/buildd/gcc-4.0-4.0.1/src/libstdc++-v3/config/abi/sparc-linux-gnu`; \
compat_baseline_name=""; \
if [ -f "/build/buildd/gcc-4.0-4.0.1/src/libstdc++-v3/config/abi/sparc-linux-gnu/baseline_symbols.txt" ]; then \
  ( \
    echo "A baseline file for $baseline_name was found."; \
    echo "Running the check-abi script ..."; \
    echo ""; \
    /usr/bin/make -C /build/buildd/gcc-4.0-4.0.1/build/sparc-linux-gnu/libstdc++-v3/testsuite \
 check-abi; \
  ) >> debian/README.libstdc++-baseline; \
else \
  ( \
    echo "No baseline file found for $baseline_name."; \
    echo "Generating a new baseline file ..."; \
    echo ""; \
  ) >> debian/README.libstdc++-baseline; \
  mkdir /build/buildd/gcc-4.0-4.0.1/src/libstdc++-v3/config/abi/sparc-linux-gnu; \
  /usr/bin/make -C /build/buildd/gcc-4.0-4.0.1/build/sparc-linux-gnu/libstdc++-v3/testsuite new-abi-baseline; \
  cat /build/buildd/gcc-4.0-4.0.1/src/libstdc++-v3/config/abi/sparc-linux-gnu/baseline_symbols.txt >> debian/README.libstdc++-baseline; \
fi
make[2]: *** No rule to make target `current_symbols.txt', needed by `check-abi'. Stop.
make[1]: *** [debian/README.libstdc++-baseline] Error 2
make[1]: Leaving directory `/build/buildd/gcc-4.0-4.0.1'
make: *** [binary-arch] Error 2

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

Version that we don't ship, it doesn't affect us.

Revision history for this message
In , Matthias Klose (doko-cs) wrote : Re: Bug#330101: gcc-4.0: ftbfs [sparc] make[2]: *** No rule to make target `current_symbols.txt'

Blars Blarson writes:
> Package: gcc-4.0
> Version: 4.0.1-9
> Severity: serious
> Justification: fails to build from source
>
> gcc-4.0 failed to build on a sparc buildd, but succeeded on my sparc
> pbuilder. Possible reasons for this include timestamp scew, more
> recent kernel version on my pbuilder, and more recent
> build-dependancies.

no, no pty's available. closing this report, this is not package
specific, and we don't have a buildd pseudo package for submitting bug
reports.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 28 Sep 2005 22:44:50 +0200
From: Matthias Klose <email address hidden>
To: Blars Blarson <email address hidden>, <email address hidden>
Subject: Re: Bug#330101: gcc-4.0: ftbfs [sparc] make[2]: *** No rule to make target
 `current_symbols.txt'

Blars Blarson writes:
> Package: gcc-4.0
> Version: 4.0.1-9
> Severity: serious
> Justification: fails to build from source
>
> gcc-4.0 failed to build on a sparc buildd, but succeeded on my sparc
> pbuilder. Possible reasons for this include timestamp scew, more
> recent kernel version on my pbuilder, and more recent
> build-dependancies.

no, no pty's available. closing this report, this is not package
specific, and we don't have a buildd pseudo package for submitting bug
reports.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.