FTBFS on Noble
Bug #2055689 reported by
Danilo Egea Gondolfo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| beep (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
It's failing with
<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
cc1: all warnings being treated as errors
Related branches
~danilogondolfo/ubuntu/+source/beep:fix_ftbfs
- Lena Voytek (community): Approve
- git-ubuntu import: Pending requested
-
Diff: 67 lines (+35/-1)4 files modifieddebian/changelog (+8/-0)
debian/control (+2/-1)
debian/patches/dont_redefine_FORTIFY_SOURCE.patch (+24/-0)
debian/patches/series (+1/-0)
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in beep (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package beep - 1.4.9-1.1ubuntu1
---------------
beep (1.4.9-1.1ubuntu1) noble; urgency=medium
* debian/
_FORTIFY_SOURCE is already defined from dpkg-buildflags and is causing a
FTBFS due to redefinition.
-- Danilo Egea Gondolfo <email address hidden> Fri, 01 Mar 2024 12:55:39 +0000