Your message dated Fri, 15 Nov 2024 15:20:00 +0000
with message-id <e1tby76-0044so...@fasolo.debian.org>
and subject line Bug#1087562: fixed in pcre2 10.44-3
has caused the Debian Bug report #1087562,
regarding pcre2: FTBFS on mips64el: ld: unrecognised emulation mode: elf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1087562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pcre2
Version: 10.44-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mips64el

This looks like it might be a problem with some toolchain component
(but I don't know which one), so please reassign and set "affects" on
src:pcre2 as appropriate.

pcre2's build system seems to have somehow got the idea that
`/usr/bin/ld -m elf` is the correct linker, for whatever reason (I don't
know where this is coming from, I can't find it hard-coded in pcre2 or
in libtool). But that is not a mode that works on mips64el:

https://buildd.debian.org/status/fetch.php?pkg=pcre2&arch=mips64el&ver=10.44-2&stamp=1731663153&raw=0
> checking if the linker (/usr/bin/ld) is GNU ld... yes
...
> checking whether the gcc linker (/usr/bin/ld -m elf) supports shared 
> libraries... /usr/bin/ld: unrecognised emulation mode: elf
> Supported emulations: elf64ltsmip elf64btsmip elf32ltsmipn32 elf32btsmipn32 
> elf32ltsmip elf32btsmip
> no

and as a result it unintentionally builds the libpcre2* family of
libraries as static-only, resulting in incomplete binary packages:

> libtool: install: /usr/bin/install -c .libs/libpcre2-posix.lai 
> /<<PKGBUILDDIR>>/debian/tmp/usr/lib/mips64el-linux-gnuabi64/libpcre2-posix.la
...
> libtool: install: /usr/bin/install -c .libs/libpcre2-posix.a 
> /<<PKGBUILDDIR>>/debian/tmp/usr/lib/mips64el-linux-gnuabi64/libpcre2-posix.a
> libtool: install: chmod 644 
> /<<PKGBUILDDIR>>/debian/tmp/usr/lib/mips64el-linux-gnuabi64/libpcre2-posix.a
> libtool: install: ranlib 
> /<<PKGBUILDDIR>>/debian/tmp/usr/lib/mips64el-linux-gnuabi64/libpcre2-posix.a
...
> dh_install: warning: libpcre2-posix3 missing files: 
> debian/tmp/usr/lib/*/libpcre2-posix.so.*
...
> dh_install: error: missing files, aborting

The same new upstream release of pcre2 failed in the same way in
experimental on 2024-11-08, so I'm surprised that it was re-uploaded to
unstable without checking experimental buildd logs for a successful build.

The most recent successful build of pcre2 was 10.43-1 back in February,
which used "ld -m elf64ltsmip".

util-linux is an example of an Autotools package that was uploaded to
unstable more recently (2024-11-03) and it also used "ld -m elf64ltsmip".

I see two possibilities for the cause of this bug:

1. there is something different about pcre2 that causes detection of the
   correct ld mode to fail; or
2. some dependency changed between 2024-11-03 and now

Perhaps someone who is better at toolchains than me can figure this out?

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: pcre2
Source-Version: 10.44-3
Done: Matthew Vernon <matt...@debian.org>

We believe that the bug you reported is fixed in the latest version of
pcre2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1087...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthew Vernon <matt...@debian.org> (supplier of updated pcre2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 15 Nov 2024 14:47:09 +0000
Source: pcre2
Architecture: source
Version: 10.44-3
Distribution: unstable
Urgency: medium
Maintainer: Matthew Vernon <matt...@debian.org>
Changed-By: Matthew Vernon <matt...@debian.org>
Closes: 1087562 1087564
Changes:
 pcre2 (10.44-3) unstable; urgency=medium
 .
   * Use dh_autoreconf to fix FTBFS on mips64el (Closes: #1087562)
   * Cherry-pick upstream commit to fix 32-bit issue (Closes: #1087564)
Checksums-Sha1:
 687278762381a28e27e507b047973853133e1a93 2340 pcre2_10.44-3.dsc
 9daa558a544321a5924b5c16e236479079fb7432 15961 pcre2_10.44-3.diff.gz
Checksums-Sha256:
 ae1fa2e826cc1b0173f812d0fff2790850830ad6a34b9e210ceca191b008ee2b 2340 
pcre2_10.44-3.dsc
 73596763aea95fa9a325513cb09f6f1fe3410fa5c72732ce8a021537e89c49bd 15961 
pcre2_10.44-3.diff.gz
Files:
 522d3d7d2c852e462ba1b748d217343a 2340 libs optional pcre2_10.44-3.dsc
 70693bf37cc532d106bf4a51651a3f38 15961 libs optional pcre2_10.44-3.diff.gz

-----BEGIN PGP SIGNATURE-----

iQJHBAEBCgAxFiEEuk75yE35bTfYoeLUEvTSHI9qY8gFAmc3Yb0THG1hdHRoZXdA
ZGViaWFuLm9yZwAKCRAS9NIcj2pjyKbCD/kBG2gq3icScOokSm3xyJ5SRmGwBVCs
gWGOpxgH1fQhjvmJCzfRfBn4s2OQPoxIXoDLjIGuB+l/eX0w3ob896J/UR6lkpBt
bDPr9jWerTIEgYNk5olTWLKxrf2egwINLecCThd01WpOb4ngQGIwqqsFDf8DIKFv
JOK1D563Lcu5cjb7emCVB+JcoZFwK2d2qHecY6posw6daUk9Y2YEMC2niE3/AdES
Sf7iAVgbBsXN2utup2n3pdVCiKCBPtgYXs3+/5k/hXe/vnxT2I1KI63lKD87pdVr
iikdjveg7bRh3xVG4UN1Tb00zWjoXuiaCE4AOIfj5eHBe2MZCtZGvQckVKMT5Pg1
Ll5GQiHorpH/vlIkRwuKqaynFV+LZAkM3Ho0r4taojrYNiCnlvtl2Ch6rLtKsp2O
dOpElDSbeTz4eaBBROYdEnVdHOLAiTm2rMmLUxlye0lDkjaXlyKqaV5+crJNnCeG
ZFdIqy7G83FScL/kGEioU1ZYVBiIN6A/GaoEkVC5UmfMjikzY5VRc56x1xQsZLxJ
PJfWbwMuYNNaMlbsZ2mIopR9BvVFgijB2ACdn9k3HU98YkQ73F7bBP3ZYunybCE1
7M6kblUsSnGEEgwV7aRevXKlaLiDZWoBxeQnZsvi7IeIVbgRCTTqvOTy97VPo1VK
FSXiywdpKNIfKQ==
=ewFJ
-----END PGP SIGNATURE-----

Attachment: pgpEYWyL5SyDD.pgp
Description: PGP signature


--- End Message ---

Reply via email to