Le 30/04/2014 16:19, Patrick Baggett a écrit :
On Wed, Apr 30, 2014 at 8:42 AM, Sébastien Bernard <sbern...@nerim.net
<mailto:sbern...@nerim.net>> wrote:
Le 30/04/2014 15:39, Patrick Baggett a écrit :
I tried to build the gcc-4.8-4.8.2-20 and the build is
broken. libstdc++ and lib64stdc++ are not build, neither are
build libgcc1.
The last good build (with the missing libraries) is 4.8.2-16.
Something broken on -20 and -21.
Oh, I see what you're saying. I get lib64stdc++-dev /
libstdc++-dev, but not the base lib64stdc++/libstdc++
And yeah, libgcc1 just isn't built, which is a major problem.
Maybe we need to look at diffs in the "debian" directory.
Patrick
Indeed, the last good build seems to be gcc-4.8-4.8.2-19.
Look at the changelog for the -20 they seems to have done
something on the sparc that blocks the generation of the libraries.
Is there a direct way to view the changelog and/or diff from the web?
Patrick
I found this url :
http://metadata.ftp-master.debian.org/changelogs//main/g/gcc-4.8/gcc-4.8_4.8.2-21_changelog
Here's the entry I suspect for all our troubles:
gcc-4.8 (4.8.2-20) unstable; urgency=medium
* Update to SVN 20140423 (r209678) from the gcc-4_8-branch.
* Explicitly configure with --disable-multilib on sparc64 when no
multilibs are requested (Helmut Grohne). Closes: #743342.
* Update powerpcspe patches for the branch (Helmut Grohne). Closes:
#743718.
* Remove more mudflap left overs. Addresses: #742606.
* Adjust common_libs, libraries common to GCC 4.9.
* Disable running the testsuite on kfreebsd, hangs the buildds.
* Stop build packages built by GCC 4.9.
-- Matthias Klose <d...@debian.org> Wed, 23 Apr 2014 11:13:07 +0200
Seb
