Kernel: Linux 2.6.38-rc6+ (SMP w/12 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libgcc1 depends on:
ii gcc-4.6-base 4.6.0-10 The GNU Compiler Collection (base
ii libc6 2.13-7 Embedded GNU C Library: Shared lib
libgcc1 recommends no packages.
libgcc1 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTikvvxqV0OoB0-em2oKzSgLUJLqn5g@mail.gmail.com">http://lists.debian.org/BANLkTikvvxqV0OoB0-em2oKzSgLUJLqn5g@mail.gmail.com
06-27-2011, 02:39 PM
Ludovic Brenta
Bug#631817: libgcc1: missing link libgccc_s.so -> libgcc_s.so.1
reassign 631627 gcc-4.6
reassign 631817 gcc-4.6
severity 631817 grave
merge 631627 631817
clone 631627 -1
reassign -1 gcc-4.4
thanks
Pedro Larroy writes:
> The link libgccc_s.so -> libgcc_s.so.1 is missing in /lib so link
> fails when this library is needed
This link is not supposed to be in libgcc1 (run-time package) but in
gcc-4.6 (build-time package). It seems that the transition to multilib
introduced this bug. Could you please tell me whether these two files
And please tell us what libgcc_s.so points to exactly.
I suspect that one of these paths are wrong, or the symlink is wrong, or
the compiler driver looks in the wrong place.
The same problem exists with gcc-4.4; cloning this bug accordingly.
--
Ludovic Brenta.
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: ba0f9e3212d3c92edd73f8ba2ce98470@localhost">http://lists.debian.org/ba0f9e3212d3c92edd73f8ba2ce98470@localhost
06-27-2011, 03:03 PM
Pedro Larroy
Bug#631817: libgcc1: missing link libgccc_s.so -> libgcc_s.so.1
l /lib/x86_64-linux-gnu/libgcc_s.so.1
ls: cannot access /lib/x86_64-linux-gnu/libgcc_s.so.1: No such file or directory
l /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6/
ls: cannot access /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6/:
No such file or directory
dpkg -l | grep gcc
ii gcc 4:4.6.0-6
GNU C compiler
ii gcc-4.2-base 4.2.4-6
The GNU Compiler Collection (base package)
ii gcc-4.3 4.3.5-5
The GNU C compiler
ii gcc-4.3-base 4.3.5-5
The GNU Compiler Collection (base package)
ii gcc-4.4 4.4.6-6
GNU C compiler
ii gcc-4.4-base 4.4.6-6
GCC, the GNU Compiler Collection (base package)
ii gcc-4.4-doc 4.4.4.nf1-1
documentation for the GNU compilers (gcc, gobjc, g++)
ii gcc-4.4-multilib 4.4.6-6
GNU C compiler (multilib files)
ii gcc-4.5 4.5.3-3
The GNU C compiler
ii gcc-4.5-base 4.5.3-3
The GNU Compiler Collection (base package)
ii gcc-4.5-multilib 4.5.3-3
The GNU C compiler (multilib files)
ii gcc-4.6 4.6.0-10
The GNU C compiler
ii gcc-4.6-base 4.6.0-10
The GNU Compiler Collection (base package)
ii gcc-4.6-multilib 4.6.0-10
The GNU C compiler (multilib files)
ii gcc-doc 5:3
documentation for the GNU compilers (gcc, gobjc, g++)
ii gcc-doc-base 4.4.4.nf1-1
several GNU manual pages
ii gcc-multilib 4:4.6.0-6
GNU C compiler (multilib files)
ii gccxml 0.9.0+cvs20110506-1
XML output extension to GCC
ii lib32gcc1 1:4.6.0-10
GCC support library (32 bit Version)
ii libgcc1 1:4.6.0-10
GCC support library
On Mon, Jun 27, 2011 at 4:39 PM, Ludovic Brenta
<ludovic@ludovic-brenta.org> wrote:
>
> reassign 631627 gcc-4.6
> reassign 631817 gcc-4.6
> severity 631817 grave
> merge 631627 631817
> clone 631627 -1
> reassign -1 gcc-4.4
> thanks
>
> Pedro Larroy writes:
>> The link libgccc_s.so -> libgcc_s.so.1 is missing in /lib so link
>> fails when this library is needed
>
> This link is not supposed to be in libgcc1 (run-time package) but in
> gcc-4.6 (build-time package). *It seems that the transition to multilib
> introduced this bug. *Could you please tell me whether these two files
> exist on your system:
>
> on amd64:
>
> /lib/x86_64-linux-gnu/libgcc_s.so.1
> (provided by package libgcc1)
>
> /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6/libgcc_s.so
> (provided by package gcc-4.6)
>
> on i386:
>
> /lib/i386-linux-gnu/libgcc_s.so.1
> (provided by package libgcc1)
>
> /usr/lib/i386-linux-gnu/gcc/i486-linux-gnu/4.6/libgcc_s.so
> (provided by package gcc-4.6)
>
> And please tell us what libgcc_s.so points to exactly.
>
> I suspect that one of these paths are wrong, or the symlink is wrong, or
> the compiler driver looks in the wrong place.
>
> The same problem exists with gcc-4.4; cloning this bug accordingly.
>
> --
> Ludovic Brenta.
>
>
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTim6Fuv-0tEHnhRmR+=7hJMabOah9Q@mail.gmail.com">http://lists.debian.org/BANLkTim6Fuv-0tEHnhRmR+=7hJMabOah9Q@mail.gmail.com
06-27-2011, 03:07 PM
Ludovic Brenta
Bug#631817: libgcc1: missing link libgccc_s.so -> libgcc_s.so.1
Pedro Larroy wrote:
> l /lib/x86_64-linux-gnu/libgcc_s.so.1
> ls: cannot access /lib/x86_64-linux-gnu/libgcc_s.so.1: No such file or
> directory
>
> l /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6/
Further research indicates that the version of gcc-4.6 currently in
testing is not yet multiarch-aware; the first version with multiarch was
4.6.0-12; the latest version is 4.6.0-14. It should have migrated to
testing five days ago but hasn't. The reasons are unclear; the PTS says
the package is out of date on powerpc but the build succeeded on
2011-06-18. Could someone please allow 4.6.0-14 to migrate?
Pedro, could you please try to reproduce the problem with gcc-4.6
(=4.6.0-14)? (i.e. install it manually with dpkg, or update your system to
sid, or create a sid chroot)
--
Ludovic Brenta.
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4680651ef6405c03c2708606869b7725@localhost">http://lists.debian.org/4680651ef6405c03c2708606869b7725@localhost
06-27-2011, 06:36 PM
"Adam D. Barratt"
Bug#631817: libgcc1: missing link libgccc_s.so -> libgcc_s.so.1
On Mon, 2011-06-27 at 17:07 +0200, Ludovic Brenta wrote:
> Further research indicates that the version of gcc-4.6 currently in
>
> testing is not yet multiarch-aware; the first version with multiarch was
>
> 4.6.0-12; the latest version is 4.6.0-14. It should have migrated to
>
> testing five days ago but hasn't. The reasons are unclear;
How are they unclear? The output generated by britney and displayed by
the PTS, grep-excuses, etc. indicates precisely why the package hadn't
migrated.
> the PTS says
>
> the package is out of date on powerpc but the build succeeded on
>
> 2011-06-18.
Indeed. However, the result of that build was never uploaded, so the
package was still out-of-date in the archive.
That's somewhat irrelevant now, however, as a new version of gcc-4.6
(4.6.1-1) was uploaded earlier today, so the migration cycle has been
reset.
> Could someone please allow 4.6.0-14 to migrate?
Commenting in bug reports is not a means of contacting the Release
Team...
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1309199770.25674.9.camel@hathi.jungle.funky-badger.org">http://lists.debian.org/1309199770.25674.9.camel@hathi.jungle.funky-badger.org
Bug#631817: libgcc1: missing link libgccc_s.so -> libgcc_s.so.1
