Am Montag, den 03.02.2020, 18:59 +0100 schrieb Matthias Klose:
> $ dpkg -S libgcc_s.so.1
> libgcc-s1:amd64: /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
> libgcc1: /lib/libgcc_s.so.1
>
> if you need the library in /lib, make sure that you depend on
> libgcc1, else it's
> found in /usr/lib/.
>
> I'm f
gcc-7_7.5.0-4_arm64.changes uploaded successfully to localhost
along with the files:
cpp-7-dbgsym_7.5.0-4_arm64.deb
cpp-7_7.5.0-4_arm64.deb
g++-7-dbgsym_7.5.0-4_arm64.deb
g++-7_7.5.0-4_arm64.deb
gcc-7-base_7.5.0-4_arm64.deb
gcc-7-dbgsym_7.5.0-4_arm64.deb
gcc-7-plugin-dev-dbgsym_7.5.0-
Package: libgcc1
Version: 1:10-20200202-1
Followup-For: Bug #950551
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
On both my systems running unstable, libgcc-s1 is installed, but I
don't have /usr/lib/x86_64-linux-gnu/libgcc_s.so.1. So, it seems
something removes it. I have no clue on why
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 04 Feb 2020 11:19:42 +0800
Source: gcc-defaults-mipsen
Architecture: source
Version: 1.187
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: YunQiang Su
Changes:
gcc-defa
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 03 Feb 2020 11:50:51 +0100
Source: gcc-7
Architecture: source
Version: 7.5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Matthias Klose
Changes:
gcc-7 (7.5.0-4) unsta
gcc-defaults-mipsen_1.187_source.changes uploaded successfully to localhost
along with the files:
gcc-defaults-mipsen_1.187.dsc
gcc-defaults-mipsen_1.187.tar.xz
gcc-defaults-mipsen_1.187_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
gcc-7_7.5.0-4_source.changes uploaded successfully to localhost
along with the files:
gcc-7_7.5.0-4.dsc
gcc-7_7.5.0-4.diff.gz
gcc-7_7.5.0-4_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Processing commands for cont...@bugs.debian.org:
> affects 950579 src:octomap
Bug #950579 [libgcc1] libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld:
cannot find -lgcc_s
Added indication that 950579 affects src:octomap
>
End of message, stopping processing here.
Please contact me if you ne
Source: flang
Version: 20190329-4
Severity: serious
Tags: ftbfs
...
dh_dwz -O--buildsystem=cmake
-O--builddirectory=/tmp/flang-20190329/debian/build
install -d debian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu
dwz -mdebian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu/flang-7.de
; urgency=medium
.
* Update to git 20200203 from the gcc-8 branch.
- Fix PR libgomp/93066, PR lto/89358, PR ipa/92971, PR target/93182 (AVR),
PR target/93111 (PARISC), PR rtl-optimization/92591,
PR target/92545 (AVR), PR target/92950 (S390), PR c/93072, PR c/93241,
PR c
subset kit)
libstdc++6-8-dbg - GNU Standard C++ Library v3 (debug build)
Closes: 950525
Changes:
gcc-8 (8.3.0-27) unstable; urgency=medium
.
* Update to git 20200203 from the gcc-8 branch.
- Fix PR libgomp/93066, PR lto/89358, PR ipa/92971, PR target/93182 (AVR),
PR target/93111
I can confirm this bug. After doing an apt full-upgrade, I faced the
same issue as OP. However, I was not able to fix it by downgrading
packages, but instead used a similar approach to the way described in
the btrfs bug #950556 [1].
After chrooting into the system, I changed the following file:
$
gcc-8_8.3.0-27_arm64.changes uploaded successfully to localhost
along with the files:
cpp-8-dbgsym_8.3.0-27_arm64.deb
cpp-8_8.3.0-27_arm64.deb
fixincludes-dbgsym_8.3.0-27_arm64.deb
fixincludes_8.3.0-27_arm64.deb
g++-8-dbgsym_8.3.0-27_arm64.deb
g++-8_8.3.0-27_arm64.deb
gcc-8-base_8.3.0
) unstable; urgency=medium
.
* Update to git 20200203 from the gcc-8 branch.
- Fix PR libgomp/93066, PR lto/89358, PR ipa/92971, PR target/93182 (AVR),
PR target/93111 (PARISC), PR rtl-optimization/92591,
PR target/92545 (AVR), PR target/92950 (S390), PR c/93072, PR c/93241
gcc-8_8.3.0-27_source.changes uploaded successfully to localhost
along with the files:
gcc-8_8.3.0-27.dsc
gcc-8_8.3.0-27.diff.gz
gcc-8_8.3.0-27_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
On 2020-02-03 20:21, Matthias Klose wrote:
> On 2/3/20 8:14 PM, Simon McVittie wrote:
> >> Sanity check compile stderr:
> >> /usr/bin/ld: cannot find -lgcc_s
> >> collect2: error: ld returned 1 exit status
>
> this is fixed in unstable. please retry the package build.
>
That won't work. For that
On 2/3/20 8:14 PM, Simon McVittie wrote:
>> Sanity check compile stderr:
>> /usr/bin/ld: cannot find -lgcc_s
>> collect2: error: ld returned 1 exit status
this is fixed in unstable. please retry the package build.
Processing control commands:
> affects -1 src:glib2.0 src:xterm src:hdrmerge src:esorex
Bug #950579 [libgcc1] libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld:
cannot find -lgcc_s
Added indication that 950579 affects src:glib2.0, src:xterm, src:hdrmerge, and
src:esorex
--
950579: https:/
Package: libgcc1
Version: 1:10-20200202-1
Severity: serious
Justification: FTBFS
Tags: ftbfs
Control: affects -1 src:glib2.0 src:xterm src:hdrmerge src:esorex
https://buildd.debian.org/status/fetch.php?pkg=glib2.0&arch=s390x&ver=2.62.4-2&stamp=1580755175&file=log
> Package versions:
[with linebre
On 2/3/20 3:46 PM, Felix Zielcke wrote:
> On Mon, 03 Feb 2020 15:35:21 +0200 dimit...@stinpriza.org wrote:
>> Package: libgcc1
>> Version: 1:9.2.1-25
>> Severity: grave
>> Justification: renders package unusable
>>
>> hey,
>>
>> after upgrading some latest packages on sid, i can no longer unlock
>
-9 (9.2.1-28) unstable; urgency=medium
.
* Update to git 20200203 from the gcc-9 branch.
- Fix PR fortran/93541, PR fortran/93462, PR fortran/93309.
* libgcc-dev: Don't ship a libgcc_so.1 symlink in gcclibdir. Closes: #950525.
* Allow retrying of a native build in ca
gcc-9_9.2.1-28_source.changes uploaded successfully to localhost
along with the files:
gcc-9_9.2.1-28.dsc
gcc-9_9.2.1-28.debian.tar.xz
gcc-9_9.2.1-28_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
iner: Debian GCC Maintainers
Changed-By: Matthias Klose
Closes: 950525
Changes:
gcc-9 (9.2.1-28) unstable; urgency=medium
.
* Update to git 20200203 from the gcc-9 branch.
- Fix PR fortran/93541, PR fortran/93462, PR fortran/93309.
* libgcc-dev: Don't ship a libgcc_so.1 symlink in gccli
-9 (9.2.1-27) unstable; urgency=medium
.
* Update to git 20200203 from the gcc-9 branch.
- Fix PR fortran/93541, PR fortran/93462, PR fortran/93309.
* libgcc-dev: Don't ship a libgcc_so.1 symlink in gcclibdir. Closes: #950525.
* Allow retrying of a native build in ca
iner: Debian GCC Maintainers
Changed-By: Matthias Klose
Closes: 950525
Changes:
gcc-9 (9.2.1-27) unstable; urgency=medium
.
* Update to git 20200203 from the gcc-9 branch.
- Fix PR fortran/93541, PR fortran/93462, PR fortran/93309.
* libgcc-dev: Don't ship a libgcc_so.1 symlink in gccli
On 2/3/20 2:27 PM, Anatoly Pugachev wrote:
> Package: libgcc1
> Version: 1:10-20200202-1
> Severity: important
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> apt update && apt upgrade -y
>
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>
gcc-9_9.2.1-27_source.changes uploaded successfully to localhost
along with the files:
gcc-9_9.2.1-27.dsc
gcc-9_9.2.1-27.debian.tar.xz
gcc-9_9.2.1-27_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
On Mon, 03 Feb 2020 15:35:21 +0200 dimit...@stinpriza.org wrote:
> Package: libgcc1
> Version: 1:9.2.1-25
> Severity: grave
> Justification: renders package unusable
>
> hey,
>
> after upgrading some latest packages on sid, i can no longer unlock
luks
> partition and boot. message:
>
> "Please u
Package: libgcc1
Version: 1:9.2.1-25
Severity: grave
Justification: renders package unusable
hey,
after upgrading some latest packages on sid, i can no longer unlock luks
partition and boot. message:
"Please unlock disk rootfs:
libgcc_s.so.1 must be installed for pthread-cancel to work
Aborted"
Package: libgcc1
Version: 1:10-20200202-1
Severity: important
Dear Maintainer,
* What led up to the situation?
apt update && apt upgrade -y
* What exactly did you do (or not do) that was effective (or
ineffective)?
before upgrade libgcc1:
ii libgcc1:sparc64 1:9.2.1-25 sparc64
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 02 Feb 2020 21:01:01 +0100
Source: gcc-9
Binary: cpp-9 cpp-9-dbgsym g++-9 g++-9-dbgsym g++-9-multilib gcc-9 gcc-9-base
gcc-9-dbgsym gcc-9-multilib gcc-9-plugin-dev gcc-9-plugin-dev-dbgsym
gcc-9-test-results gccg
31 matches
Mail list logo
