Bug#745938: the future of sparc in unstable

[Steven Chamberlain]

On 17:06, Bob Bib wrote:
> AFAIK, the SPARC32 toolchain is no longer supported upstream,
> while Debian 'sparc' port has only 32-bit userland,
> with kernel 64 bit-only.

A lot of people have repeated this like rumour, but were unable to
point me to something official when asked.  All I can find is this
statement:

https://release.debian.org/jessie/arch_qualify.html
| sparc
| Upstream Support
|
| According to the gcc maintainer 32bit code generation as we use it is
| no longer supported upstream and we should aim for a switch to 64bit
| userland anytime soon.

Actually confirming this with upstream would be a good idea IMHO before
acting on it.

sparc64 still lags way behind sparc (and even hurd-i386) in archive
coverage so likely that needs to be improved first:
http://buildd.debian-ports.org/stats/

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#745938: the future of sparc in unstable

[Bob Bib]

AFAIK, the SPARC32 toolchain is no longer supported upstream,
while Debian 'sparc' port has only 32-bit userland,
with kernel 64 bit-only.

So from my point of view,
the 'sparc' port should be finally DROPPED
in favor of the 'sparc64' port
which should be migrated from debian-ports
into the official archives
(maybe, it should be initially put there in a 'safe' mode,
unstable-only, like the 'hurd' is now?)


Best wishes, Bob


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#745938: the future of sparc in unstable

[Hermann Lauer]

Just to let all know: Here are Sun Enterprise 880,480,280 and 450
running wheezy (and still squeeze) fine, there are only minor issues with
those kernels (look at the linux sparc mailing list and in the debian BTS if
you are interested - or ask) here. In the small timeslots left I even
compiled sometimes vanilla kernels (make deb-pkg), and it's a pity
(but understandable) that jessie sparc will not be.

Huge thanks at this point to all the past releases sparc maintainers !  

Time is always the problem but if it helps I can offer hosting
of a build machine out of our Sun Enterprises, if that would help.

What is the maillist to follow sparc-port issues ?

Thanks, Hermann

-- 
Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres 
Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg
IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224
Email: hermann.la...@iwr.uni-heidelberg.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#745938: the future of sparc in unstable

[Patrick Baggett]

I have SILO v1.4.14, but it has the git [1] patches from 2012-08-19, which
includes quite a few fixes from the 2008-06-12 release. Particularly, it
includes a number of ext2/ext4 boot fixes and some sun4v and sun4u boot
fixes. The remaining patches after that are for "tilo" which is some kind
of TFTP loader.

TL;DR - though it isn't the newest, it should be more or less up to date
for bug fixes.

[1] http://git.kernel.org/cgit/linux/kernel/git/davem/silo.git/log/



On Thu, May 1, 2014 at 6:10 PM, Kieron Gillespie  wrote:

> Well it is a good start. =D
>
> There are still complaints, though haven't seen the bug reports, that
> modern kernel's are unstable on certain peices of hardware. Personally I
> can't reproduce any of these issues, I have rolled out the latest kernel
> for a while now on some of my sparc systems, my T2000 has an uptime of
> about 80days and it's running wheezy but using a vanilla 3.13.9 build.
> There is also some problems with the kernel hanging in the early stages of
> the boot process, though once again I have not seen this. What the sparc
> port needs are a couple of people to become familiar with the Debian
> build process and to find major bugs report and fix them.
>
> I haven't checked but I think that SILO is currently a version or two
> ahead of what debian is using for it's installs. That might be the issue.
>
> Wish I had more time to invest in this.
>
> -Kieron
>
>
> On Thu, May 1, 2014 at 6:21 PM, Patrick Baggett  > wrote:
>
>> BTW, the sparc buildd looks like gcc 4-8.2-21 is successful and so is
>> gcc-4.9.0-1. I've installed them from sid. Crisis averted?
>>
>> Patrick
>>
>>
>> On Wed, Apr 30, 2014 at 4:04 PM, Sébastien Bernard wrote:
>>
>>>  Le 30/04/2014 20:36, Patrick Baggett a écrit :
>>>
>>>
>>>
>>>
>>> On Wed, Apr 30, 2014 at 1:13 PM, Ivo De Decker wrote:
>>>
 Hi,

 On Wed, Apr 30, 2014 at 03:42:39PM +0200, Sébastien Bernard wrote:
 > 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.

  A number of binaries are now built by gcc-4.9 instead of gcc-4.8. As
 there is
 no build of gcc-4.9 on sparc, these binaries are missing.

 https://buildd.debian.org/status/logs.php?pkg=gcc-4.9&arch=sparc

 So if you want to fix the sparc issue, you probably need to get gcc-4.9
 to
 build there. When doing that, you need to start from a gcc-4.8 version
 from
 before the change, as newer version are not functional without the
 packages
 from gcc-4.9.

  ???
>>> I thought jessie was using gcc-4.8 and not gcc-4.9
>>>
>>>  OK, so we additionally need to look into why gcc-4.9 is not
>>> installable?
>>>
>>>  Patrick
>>>
>>>
>>> No, we don't. Period.
>>>
>>> I built the gcc-4.8-4.8-19, and all the binaries are there.
>>> I'm going to involve the gcc maintainer cause what they did broke
>>> completely the build be it jessie or sid.
>>>
>>> We have libgcc1, lib64gcc1, libstdc++6,  and libstdc++6 available from
>>> the repositories in version 4.8.2-19.
>>> But, the new builds -20 and -21 have overriden all the other packages
>>> from -19 since they have been build ok.
>>> So, now, we have nothing to install because gcc-base-4.8_4.8.2-20
>>> depends on libgcc1-4.8.2_4.8.2-20 which isn't build (this is the message
>>> from apt-get).
>>>
>>> And this is not solvable, we're halfway through, with partial -19
>>> packages and missing packages -20.
>>>
>>> And if you think it has zero impact, think twice. The debootstrap is not
>>> able to build a sid install because of this.
>>> So, meanwhile, I'll setup a mini directory with the packages availables
>>> (I need to remember how to setup a debian repository again).
>>>
>>> All in all, this broken package has blocked the complete buildd, since
>>> there is no more libgcc1 and no more libstdc++ installable.
>>>
>>> Did I say there is no gcc-4.9 ?
>>>
>>> Here is the recipe for disaster for sparc.
>>>
>>> Seb
>>>
>>
>>
>

Bug#745938: the future of sparc in unstable

[Kieron Gillespie]

Well it is a good start. =D

There are still complaints, though haven't seen the bug reports, that
modern kernel's are unstable on certain peices of hardware. Personally I
can't reproduce any of these issues, I have rolled out the latest kernel
for a while now on some of my sparc systems, my T2000 has an uptime of
about 80days and it's running wheezy but using a vanilla 3.13.9 build.
There is also some problems with the kernel hanging in the early stages of
the boot process, though once again I have not seen this. What the sparc
port needs are a couple of people to become familiar with the Debian build
process and to find major bugs report and fix them.

I haven't checked but I think that SILO is currently a version or two ahead
of what debian is using for it's installs. That might be the issue.

Wish I had more time to invest in this.

-Kieron


On Thu, May 1, 2014 at 6:21 PM, Patrick Baggett
wrote:

> BTW, the sparc buildd looks like gcc 4-8.2-21 is successful and so is
> gcc-4.9.0-1. I've installed them from sid. Crisis averted?
>
> Patrick
>
>
> On Wed, Apr 30, 2014 at 4:04 PM, Sébastien Bernard wrote:
>
>>  Le 30/04/2014 20:36, Patrick Baggett a écrit :
>>
>>
>>
>>
>> On Wed, Apr 30, 2014 at 1:13 PM, Ivo De Decker wrote:
>>
>>> Hi,
>>>
>>> On Wed, Apr 30, 2014 at 03:42:39PM +0200, Sébastien Bernard wrote:
>>> > 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.
>>>
>>>  A number of binaries are now built by gcc-4.9 instead of gcc-4.8. As
>>> there is
>>> no build of gcc-4.9 on sparc, these binaries are missing.
>>>
>>> https://buildd.debian.org/status/logs.php?pkg=gcc-4.9&arch=sparc
>>>
>>> So if you want to fix the sparc issue, you probably need to get gcc-4.9
>>> to
>>> build there. When doing that, you need to start from a gcc-4.8 version
>>> from
>>> before the change, as newer version are not functional without the
>>> packages
>>> from gcc-4.9.
>>>
>>>  ???
>> I thought jessie was using gcc-4.8 and not gcc-4.9
>>
>>  OK, so we additionally need to look into why gcc-4.9 is not installable?
>>
>>  Patrick
>>
>>
>> No, we don't. Period.
>>
>> I built the gcc-4.8-4.8-19, and all the binaries are there.
>> I'm going to involve the gcc maintainer cause what they did broke
>> completely the build be it jessie or sid.
>>
>> We have libgcc1, lib64gcc1, libstdc++6,  and libstdc++6 available from
>> the repositories in version 4.8.2-19.
>> But, the new builds -20 and -21 have overriden all the other packages
>> from -19 since they have been build ok.
>> So, now, we have nothing to install because gcc-base-4.8_4.8.2-20 depends
>> on libgcc1-4.8.2_4.8.2-20 which isn't build (this is the message from
>> apt-get).
>>
>> And this is not solvable, we're halfway through, with partial -19
>> packages and missing packages -20.
>>
>> And if you think it has zero impact, think twice. The debootstrap is not
>> able to build a sid install because of this.
>> So, meanwhile, I'll setup a mini directory with the packages availables
>> (I need to remember how to setup a debian repository again).
>>
>> All in all, this broken package has blocked the complete buildd, since
>> there is no more libgcc1 and no more libstdc++ installable.
>>
>> Did I say there is no gcc-4.9 ?
>>
>> Here is the recipe for disaster for sparc.
>>
>> Seb
>>
>
>

Bug#745938: the future of sparc in unstable

[Patrick Baggett]

BTW, the sparc buildd looks like gcc 4-8.2-21 is successful and so is
gcc-4.9.0-1. I've installed them from sid. Crisis averted?

Patrick


On Wed, Apr 30, 2014 at 4:04 PM, Sébastien Bernard wrote:

>  Le 30/04/2014 20:36, Patrick Baggett a écrit :
>
>
>
>
> On Wed, Apr 30, 2014 at 1:13 PM, Ivo De Decker wrote:
>
>> Hi,
>>
>> On Wed, Apr 30, 2014 at 03:42:39PM +0200, Sébastien Bernard wrote:
>> > 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.
>>
>>  A number of binaries are now built by gcc-4.9 instead of gcc-4.8. As
>> there is
>> no build of gcc-4.9 on sparc, these binaries are missing.
>>
>> https://buildd.debian.org/status/logs.php?pkg=gcc-4.9&arch=sparc
>>
>> So if you want to fix the sparc issue, you probably need to get gcc-4.9 to
>> build there. When doing that, you need to start from a gcc-4.8 version
>> from
>> before the change, as newer version are not functional without the
>> packages
>> from gcc-4.9.
>>
>>  ???
> I thought jessie was using gcc-4.8 and not gcc-4.9
>
>  OK, so we additionally need to look into why gcc-4.9 is not installable?
>
>  Patrick
>
>
> No, we don't. Period.
>
> I built the gcc-4.8-4.8-19, and all the binaries are there.
> I'm going to involve the gcc maintainer cause what they did broke
> completely the build be it jessie or sid.
>
> We have libgcc1, lib64gcc1, libstdc++6,  and libstdc++6 available from the
> repositories in version 4.8.2-19.
> But, the new builds -20 and -21 have overriden all the other packages from
> -19 since they have been build ok.
> So, now, we have nothing to install because gcc-base-4.8_4.8.2-20 depends
> on libgcc1-4.8.2_4.8.2-20 which isn't build (this is the message from
> apt-get).
>
> And this is not solvable, we're halfway through, with partial -19 packages
> and missing packages -20.
>
> And if you think it has zero impact, think twice. The debootstrap is not
> able to build a sid install because of this.
> So, meanwhile, I'll setup a mini directory with the packages availables (I
> need to remember how to setup a debian repository again).
>
> All in all, this broken package has blocked the complete buildd, since
> there is no more libgcc1 and no more libstdc++ installable.
>
> Did I say there is no gcc-4.9 ?
>
> Here is the recipe for disaster for sparc.
>
> Seb
>

Bug#745938: the future of sparc in unstable

[Sébastien Bernard]

Le 30/04/2014 20:36, Patrick Baggett a écrit :




On Wed, Apr 30, 2014 at 1:13 PM, Ivo De Decker > wrote:


Hi,

On Wed, Apr 30, 2014 at 03:42:39PM +0200, Sébastien Bernard wrote:
> 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.

A number of binaries are now built by gcc-4.9 instead of gcc-4.8.
As there is
no build of gcc-4.9 on sparc, these binaries are missing.

https://buildd.debian.org/status/logs.php?pkg=gcc-4.9&arch=sparc

So if you want to fix the sparc issue, you probably need to get
gcc-4.9 to
build there. When doing that, you need to start from a gcc-4.8
version from
before the change, as newer version are not functional without the
packages
from gcc-4.9.

???
I thought jessie was using gcc-4.8 and not gcc-4.9

OK, so we additionally need to look into why gcc-4.9 is not installable?

Patrick


No, we don't. Period.

I built the gcc-4.8-4.8-19, and all the binaries are there.
I'm going to involve the gcc maintainer cause what they did broke 
completely the build be it jessie or sid.


We have libgcc1, lib64gcc1, libstdc++6,  and libstdc++6 available from 
the repositories in version 4.8.2-19.
But, the new builds -20 and -21 have overriden all the other packages 
from -19 since they have been build ok.
So, now, we have nothing to install because gcc-base-4.8_4.8.2-20 
depends on libgcc1-4.8.2_4.8.2-20 which isn't build (this is the message 
from apt-get).


And this is not solvable, we're halfway through, with partial -19 
packages and missing packages -20.


And if you think it has zero impact, think twice. The debootstrap is not 
able to build a sid install because of this.
So, meanwhile, I'll setup a mini directory with the packages availables 
(I need to remember how to setup a debian repository again).


All in all, this broken package has blocked the complete buildd, since 
there is no more libgcc1 and no more libstdc++ installable.


Did I say there is no gcc-4.9 ?

Here is the recipe for disaster for sparc.

Seb

Bug#745938: the future of sparc in unstable

[Patrick Baggett]

On Wed, Apr 30, 2014 at 1:13 PM, Ivo De Decker wrote:

> Hi,
>
> On Wed, Apr 30, 2014 at 03:42:39PM +0200, Sébastien Bernard wrote:
> > 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.
>
> A number of binaries are now built by gcc-4.9 instead of gcc-4.8. As there
> is
> no build of gcc-4.9 on sparc, these binaries are missing.
>
> https://buildd.debian.org/status/logs.php?pkg=gcc-4.9&arch=sparc
>
> So if you want to fix the sparc issue, you probably need to get gcc-4.9 to
> build there. When doing that, you need to start from a gcc-4.8 version from
> before the change, as newer version are not functional without the packages
> from gcc-4.9.
>
> ???
I thought jessie was using gcc-4.8 and not gcc-4.9

OK, so we additionally need to look into why gcc-4.9 is not installable?

Patrick

Bug#745938: the future of sparc in unstable

[Ivo De Decker]

Hi,

On Wed, Apr 30, 2014 at 03:42:39PM +0200, Sébastien Bernard wrote:
> 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.

A number of binaries are now built by gcc-4.9 instead of gcc-4.8. As there is
no build of gcc-4.9 on sparc, these binaries are missing.

https://buildd.debian.org/status/logs.php?pkg=gcc-4.9&arch=sparc

So if you want to fix the sparc issue, you probably need to get gcc-4.9 to
build there. When doing that, you need to start from a gcc-4.8 version from
before the change, as newer version are not functional without the packages
from gcc-4.9.

BTW this is listed in the gcc-4.8 changelog as
  * Stop build packages built by GCC 4.9.


Cheers,

Ivo


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#745938: the future of sparc in unstable

[Steven Chamberlain]

On 30/04/14 15:19, Patrick Baggett wrote:
> On Wed, Apr 30, 2014 at 8:42 AM, Sébastien Bernard  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++

> 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?

I don't think so.  So I grabbed both versions from snapshots.d.o and
compared them with debdiff.  Ignoring src/ and debian/patches/ I got the
attached diff.  The relevant change for sparc is in the last hunk.

After an initial attempt in 4.8.2-19 which didn't work due to a typo,
version 4.8.2-20 disabled multilib for sparc64.  I think maybe
not-building some of the packages you mention could be deliberate and/or
their names have changed.

Possibly the package's build dependencies need to be different now on
sparc and/or sparc64.  (e.g. perhaps 32-bit sparc build should no longer
build-depend on lib64gcc1?)

The old packages likely also need to be de-crufted by ftpmaster
("ANAIS"?) or else the whole source package will be considered
"out-of-date" on that arch.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org
diff -u gcc-4.8-4.8.2/debian/changelog gcc-4.8-4.8.2/debian/changelog
--- gcc-4.8-4.8.2/debian/changelog
+++ gcc-4.8-4.8.2/debian/changelog
@@ -1,3 +1,16 @@
+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   Wed, 23 Apr 2014 11:13:07 +0200
+
 gcc-4.8 (4.8.2-19) unstable; urgency=medium
 
   * Update to SVN 20140404 (r209122) from the gcc-4_8-branch.
diff -u gcc-4.8-4.8.2/debian/control gcc-4.8-4.8.2/debian/control
--- gcc-4.8-4.8.2/debian/control
+++ gcc-4.8-4.8.2/debian/control
@@ -15,7 +15,7 @@
   texinfo (>= 4.3), locales, sharutils, 
   procps, zlib1g-dev, libantlr-java, python, libffi-dev, fastjar, 
libmagic-dev, libecj-java (>= 3.3.0-2), zip, libasound2-dev [ !hurd-any 
!kfreebsd-any], libxtst-dev, libxt-dev, libgtk2.0-dev (>= 2.4.4-2), 
libart-2.0-dev, libcairo2-dev, g++-4.8 [armel armhf], netbase, 
   libcloog-isl-dev (>= 0.18), libmpc-dev (>= 1.0), libmpfr-dev (>= 3.0.0-9~), 
libgmp-dev (>= 2:5.0.1~), 
-  dejagnu [!m68k !hurd-amd64 !hurd-i386 !hurd-alpha], autogen, realpath (>= 
1.9.12), chrpath, lsb-release, quilt
+  dejagnu [!m68k !hurd-amd64 !hurd-i386 !hurd-alpha !kfreebsd-amd64 
!kfreebsd-i386 !kfreebsd-alpha], autogen, realpath (>= 1.9.12), chrpath, 
lsb-release, quilt
 Build-Depends-Indep: doxygen (>= 1.7.2), graphviz (>= 2.2), ghostscript, 
texlive-latex-base, xsltproc, libxml2-utils, docbook-xsl-ns, 
 Homepage: http://gcc.gnu.org/
 XS-Vcs-Browser: http://svn.debian.org/viewsvn/gcccvs/branches/sid/gcc-4.8/
@@ -1201,107 +1201,6 @@
  On architectures with multilib support, the package contains files
  and dependencies for the non-default multilib architecture(s).
 
-Package: libgo4
-Section: libs
-Architecture: any
-Multi-Arch: same
-Pre-Depends: multiarch-support
-Provides: libgo4-armel [armel], libgo4-armhf [armhf]
-Priority: optional
-Depends: gcc-4.8-base (= ${gcc:Version}), ${shlibs:Depends}, ${misc:Depends}
-Replaces: libgo3
-Description: Runtime library for GNU Go applications
- Library needed for GNU Go applications linked against the
- shared library.
-
-Package: libgo4-dbg
-Section: debug
-Architecture: any
-Multi-Arch: same
-Provides: libgo4-dbg-armel [armel], libgo4-dbg-armhf [armhf]
-Priority: extra
-Depends: gcc-4.8-base (= ${gcc:Version}), libgo4 (= ${gcc:Version}), 
${misc:Depends}
-Description: Runtime library for GNU Go applications (debug symbols)
- Library needed for GNU Go applications linked against the
- shared library.
-
-Package: lib64go4
-Section: libs
-Architecture: i386 powerpc sparc s390 mips mipsel mipsn32 mipsn32el x32
-Priority: optional
-Depends: gcc-4.8-base (= ${gcc:Version}), ${dep:libcbiarch}, 
${shlibs:Depends}, ${misc:Depends}
-Replaces: lib64go3
-Description: Runtime library for GNU Go applications (64bit)
- Library needed for GNU Go applications linked against the
- shared library.
-
-Package: lib64go4-dbg
-Section

Bug#745938: the future of sparc in unstable

[Sébastien Bernard]

Le 30/04/2014 16:19, Patrick Baggett a écrit :




On Wed, Apr 30, 2014 at 8:42 AM, Sébastien Bernard > 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   Wed, 23 Apr 2014 11:13:07 +0200

Seb

Bug#745938: the future of sparc in unstable

[Patrick Baggett]

On Wed, Apr 30, 2014 at 8:42 AM, Sébastien Bernard 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

Bug#745938: the future of sparc in unstable

[Kieron Gillespie]

What is also weird is you have the debug package for it. So I am sure it
compiled I think there might be something wrong with the packaging for it.


On Wed, Apr 30, 2014 at 9:39 AM, Patrick Baggett
wrote:

>
>>>  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
>

Bug#745938: the future of sparc in unstable

[Sébastien Bernard]

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.


Seb

Bug#745938: the future of sparc in unstable

[Patrick Baggett]

>
>
>>  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

Bug#745938: the future of sparc in unstable

[Kieron Gillespie]

I have also been able to build the gcc 4.8.2-21 packages as well. I am not
sure what is causing the build systems so much grief when it comes to
building these packages.

Cheers,
Kieron


On Wed, Apr 30, 2014 at 9:27 AM, Patrick Baggett
wrote:

> I kicked off a gcc build (gcc-4.8_4.8.2-21) last night. It didn't have an
> errors for me. I now have a bunch of *.deb files:
>
> figgles@ghost:~/src$ ls -1 *.deb
> cpp-4.8_4.8.2-21_sparc.deb
> g++-4.8-multilib_4.8.2-21_sparc.deb
> g++-4.8_4.8.2-21_sparc.deb
> gcc-4.8-base_4.8.2-21_sparc.deb
> gcc-4.8-locales_4.8.2-21_all.deb
> gcc-4.8-multilib_4.8.2-21_sparc.deb
> gcc-4.8-plugin-dev_4.8.2-21_sparc.deb
> gcc-4.8-source_4.8.2-21_all.deb
> gcc-4.8_4.8.2-21_sparc.deb
> gcj-4.8-jdk_4.8.2-21_sparc.deb
> gcj-4.8-jre-headless_4.8.2-21_sparc.deb
> gcj-4.8-jre-lib_4.8.2-21_all.deb
> gcj-4.8-jre_4.8.2-21_sparc.deb
> gcj-4.8-source_4.8.2-21_all.deb
> gcj-4.8_4.8.2-21_sparc.deb
> gdc-4.8_4.8.2-21_sparc.deb
> gfortran-4.8-multilib_4.8.2-21_sparc.deb
> gfortran-4.8_4.8.2-21_sparc.deb
> gobjc++-4.8-multilib_4.8.2-21_sparc.deb
> gobjc++-4.8_4.8.2-21_sparc.deb
> gobjc-4.8-multilib_4.8.2-21_sparc.deb
> gobjc-4.8_4.8.2-21_sparc.deb
> lib64asan0-dbg_4.8.2-21_sparc.deb
> lib64asan0_4.8.2-21_sparc.deb
> lib64gcc-4.8-dev_4.8.2-21_sparc.deb
> lib64gfortran-4.8-dev_4.8.2-21_sparc.deb
> lib64objc-4.8-dev_4.8.2-21_sparc.deb
> lib64stdc++-4.8-dev_4.8.2-21_sparc.deb
> lib64stdc++6-4.8-dbg_4.8.2-21_sparc.deb
> libasan0-dbg_4.8.2-21_sparc.deb
> libasan0_4.8.2-21_sparc.deb
> libgcc-4.8-dev_4.8.2-21_sparc.deb
> libgcj14-awt_4.8.2-21_sparc.deb
> libgcj14-dbg_4.8.2-21_sparc.deb
> libgcj14-dev_4.8.2-21_sparc.deb
> libgcj14_4.8.2-21_sparc.deb
> libgfortran-4.8-dev_4.8.2-21_sparc.deb
> libobjc-4.8-dev_4.8.2-21_sparc.deb
> libstdc++-4.8-dev_4.8.2-21_sparc.deb
> libstdc++-4.8-doc_4.8.2-21_all.deb
> libstdc++-4.8-pic_4.8.2-21_sparc.deb
> libstdc++6-4.8-dbg_4.8.2-21_sparc.deb
>
>
>
>
> On Tue, Apr 29, 2014 at 3:12 PM, Sébastien Bernard wrote:
>
>> Le 26/04/2014 21:33, Ralf Treinen a écrit :
>>
>>  Hello,
>>>
>>> we currently have in unstable/main/sparc precisely 35491 packages, of
>>> a total of 40634 available packages, that cannot be installed in the
>>> current version of unstable:
>>>
>>> % dose-debcheck --fg Packages --deb-ignore-essential
>>> background-packages: 0
>>> foreground-packages: 40634
>>> total-packages: 40634
>>> broken-packages: 35491
>>>
>>> The most common cause seems to be that libgcc1 1:4.8.2-19 depends on
>>> gcc-4.8-base (= 4.8.2-19), and version 4.8.2-20 is in the archive. I just
>>> found this when I investigated why the daily run of my dose-debcheck
>>> script
>>> explodes the last 3 days.
>>>
>>> -Ralf.
>>>
>>>
>>>  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.
>>
>> My .002 contribution.
>>
>> Seb
>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmas...@lists.debian.org
>> Archive: https://lists.debian.org/53600797.2010...@nerim.net
>>
>>
>

Bug#745938: the future of sparc in unstable

[Patrick Baggett]

I kicked off a gcc build (gcc-4.8_4.8.2-21) last night. It didn't have an
errors for me. I now have a bunch of *.deb files:

figgles@ghost:~/src$ ls -1 *.deb
cpp-4.8_4.8.2-21_sparc.deb
g++-4.8-multilib_4.8.2-21_sparc.deb
g++-4.8_4.8.2-21_sparc.deb
gcc-4.8-base_4.8.2-21_sparc.deb
gcc-4.8-locales_4.8.2-21_all.deb
gcc-4.8-multilib_4.8.2-21_sparc.deb
gcc-4.8-plugin-dev_4.8.2-21_sparc.deb
gcc-4.8-source_4.8.2-21_all.deb
gcc-4.8_4.8.2-21_sparc.deb
gcj-4.8-jdk_4.8.2-21_sparc.deb
gcj-4.8-jre-headless_4.8.2-21_sparc.deb
gcj-4.8-jre-lib_4.8.2-21_all.deb
gcj-4.8-jre_4.8.2-21_sparc.deb
gcj-4.8-source_4.8.2-21_all.deb
gcj-4.8_4.8.2-21_sparc.deb
gdc-4.8_4.8.2-21_sparc.deb
gfortran-4.8-multilib_4.8.2-21_sparc.deb
gfortran-4.8_4.8.2-21_sparc.deb
gobjc++-4.8-multilib_4.8.2-21_sparc.deb
gobjc++-4.8_4.8.2-21_sparc.deb
gobjc-4.8-multilib_4.8.2-21_sparc.deb
gobjc-4.8_4.8.2-21_sparc.deb
lib64asan0-dbg_4.8.2-21_sparc.deb
lib64asan0_4.8.2-21_sparc.deb
lib64gcc-4.8-dev_4.8.2-21_sparc.deb
lib64gfortran-4.8-dev_4.8.2-21_sparc.deb
lib64objc-4.8-dev_4.8.2-21_sparc.deb
lib64stdc++-4.8-dev_4.8.2-21_sparc.deb
lib64stdc++6-4.8-dbg_4.8.2-21_sparc.deb
libasan0-dbg_4.8.2-21_sparc.deb
libasan0_4.8.2-21_sparc.deb
libgcc-4.8-dev_4.8.2-21_sparc.deb
libgcj14-awt_4.8.2-21_sparc.deb
libgcj14-dbg_4.8.2-21_sparc.deb
libgcj14-dev_4.8.2-21_sparc.deb
libgcj14_4.8.2-21_sparc.deb
libgfortran-4.8-dev_4.8.2-21_sparc.deb
libobjc-4.8-dev_4.8.2-21_sparc.deb
libstdc++-4.8-dev_4.8.2-21_sparc.deb
libstdc++-4.8-doc_4.8.2-21_all.deb
libstdc++-4.8-pic_4.8.2-21_sparc.deb
libstdc++6-4.8-dbg_4.8.2-21_sparc.deb




On Tue, Apr 29, 2014 at 3:12 PM, Sébastien Bernard wrote:

> Le 26/04/2014 21:33, Ralf Treinen a écrit :
>
>  Hello,
>>
>> we currently have in unstable/main/sparc precisely 35491 packages, of
>> a total of 40634 available packages, that cannot be installed in the
>> current version of unstable:
>>
>> % dose-debcheck --fg Packages --deb-ignore-essential
>> background-packages: 0
>> foreground-packages: 40634
>> total-packages: 40634
>> broken-packages: 35491
>>
>> The most common cause seems to be that libgcc1 1:4.8.2-19 depends on
>> gcc-4.8-base (= 4.8.2-19), and version 4.8.2-20 is in the archive. I just
>> found this when I investigated why the daily run of my dose-debcheck
>> script
>> explodes the last 3 days.
>>
>> -Ralf.
>>
>>
>>  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.
>
> My .002 contribution.
>
> Seb
>
>
>
> --
> To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: https://lists.debian.org/53600797.2010...@nerim.net
>
>

Bug#745938: the future of sparc in unstable

[Sébastien Bernard]

Le 26/04/2014 21:33, Ralf Treinen a écrit :

Hello,

we currently have in unstable/main/sparc precisely 35491 packages, of
a total of 40634 available packages, that cannot be installed in the
current version of unstable:

% dose-debcheck --fg Packages --deb-ignore-essential
background-packages: 0
foreground-packages: 40634
total-packages: 40634
broken-packages: 35491

The most common cause seems to be that libgcc1 1:4.8.2-19 depends on
gcc-4.8-base (= 4.8.2-19), and version 4.8.2-20 is in the archive. I just
found this when I investigated why the daily run of my dose-debcheck script
explodes the last 3 days.

-Ralf.


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.

My .002 contribution.

Seb


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#745938: the future of sparc in unstable

[Ralf Treinen]

Hello,

we currently have in unstable/main/sparc precisely 35491 packages, of
a total of 40634 available packages, that cannot be installed in the
current version of unstable:

% dose-debcheck --fg Packages --deb-ignore-essential
background-packages: 0
foreground-packages: 40634
total-packages: 40634
broken-packages: 35491

The most common cause seems to be that libgcc1 1:4.8.2-19 depends on
gcc-4.8-base (= 4.8.2-19), and version 4.8.2-20 is in the archive. I just
found this when I investigated why the daily run of my dose-debcheck script
explodes the last 3 days.

-Ralf.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org