Your message dated Sun, 24 Mar 2024 00:38:21 +0100
with message-id <[email protected]>
and subject line Re: bash: FTBFS with clang instead of gcc
has caused the Debian Bug report #787059,
regarding bash: FTBFS with clang instead of gcc
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 [email protected]
immediately.)
--
787059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787059
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash
Version: 4.3-12
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
Content-Type: multipart/mixed; boundary="===============8756920058145874366=="
MIME-Version: 1.0
From: Joseph Lee <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: bash: FTBFS with clang instead of gcc
Message-ID: <20150528071544.8425.84924.reportbug@roc-jesa>
X-Mailer: reportbug 6.6.3
Date: Thu, 28 May 2015 07:15:45 +0000
This is a multi-part MIME message sent by reportbug.
--===============8756920058145874366==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: bash
Version: 4.3-12
Severity: minor
Dear Maintainer,
Hello,
Using the rebuilding infrastructure, your package failed to build with
clang instead of because of linker error.
Error is like this:
http://clang.debian.net/status.php?version=3.6.0&key=LINK_ERROR
Full build log is available here:
http://clang.debian.net/logs/2015-03-25/bash_4.3-12_unstable_clang.log
I found that using ld.gold as linker can fix this problem.
Thanks,
Joseph
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.4-2-ARCH (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
--===============8756920058145874366==
Content-Type: text/x-diff; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="bash_clang.patch"
diff -Nru bash-4.3/debian/rules bash-4.3/debian/rules
--- bash-4.3/debian/rules 2015-01-28 16:55:12.000000000 +0000
+++ bash-4.3/debian/rules 2015-05-20 03:24:37.000000000 +0000
@@ -43,7 +43,9 @@
CFLAGS := $(shell $(dpkg_buildflags) --get CFLAGS)
CPPFLAGS := $(shell $(dpkg_buildflags) --get CPPFLAGS)
LDFLAGS := $(shell $(dpkg_buildflags) --get LDFLAGS)
-
+ifeq ($(shell $(CC) -v 2>&1 | grep -c "clang version"), 1)
+ LDFLAGS += -fuse-ld=gold
+endif
SHELL = /bin/bash
YACC = bison -y
--===============8756920058145874366==--
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.4-2-ARCH (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages bash depends on:
ii base-files 9.2
ii dash 0.5.7-4+b1
ii debianutils 4.5
ii libc6 2.19-18
ii libncurses5 5.9+20150516-2
ii libtinfo5 5.9+20150516-2
Versions of packages bash recommends:
pn bash-completion <none>
Versions of packages bash suggests:
pn bash-doc <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
According to the current https://clang.debian.net/maintainers.php, bash
can be compiled with clang 13.0.0.
--- End Message ---
