HWE snaps are building with wrong CFLAGS options
Bug #1791333 reported by
Alfonso Sanchez-Beato
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snappy-hwe-snaps |
In Progress
|
Critical
|
Alfonso Sanchez-Beato |
Bug Description
The reason for this is LP: #1791946. There is also the fact that we are compiling without -O2 all of our snaps that include autotools. That includes:
* wpa-supplicant
* bluez
* pulseaudio
* wifi-ap
Related branches
~alfonsosanchezbeato/snappy-hwe-snaps/+git/network-manager:enable-o2
Merged
into
~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager:master
at
revision 2453b39736aa2074be3cd4e2ecad5e5041d18356
- Tony Espy: Approve
- System Enablement Bot: Approve (continuous-integration)
-
Diff: 13 lines (+2/-0)1 file modifiedsnapcraft.yaml (+2/-0)
~alfonsosanchezbeato/snappy-hwe-snaps/+git/modem-manager:optimize
Merged
into
~snappy-hwe-team/snappy-hwe-snaps/+git/modem-manager:master
at
revision 0b9edf1a164cf476c7afa7cdc8fd317a8dd54b2a
- Tony Espy: Approve
- System Enablement Bot: Approve (continuous-integration)
-
Diff: 31 lines (+6/-0)1 file modifiedsnapcraft.yaml (+6/-0)
Changed in snappy-hwe-snaps: | |
status: | New → Incomplete |
assignee: | nobody → Alfonso Sanchez-Beato (alfonsosanchezbeato) |
description: | updated |
Changed in snappy-hwe-snaps: | |
status: | Incomplete → Confirmed |
summary: |
- New builds of snap packages for HWE snaps have much bigger size than - before + HWE snaps are building with wrong CFLAGS options |
Changed in snappy-hwe-snaps: | |
importance: | Undecided → Critical |
status: | Confirmed → In Progress |
description: | updated |
To post a comment you must log in.
As stated before, we need to find the root cause before we submit a fix. Your description doesn't mention what version of snapcraft you used.
I checked the changelog for snapcraft 2.43, which was released recently and couldn't find any changes that might've caused this problem:
https:/ /github. com/snapcore/ snapcraft/ releases/ tag/2.43
I reverted back to 2.42.1, and the problem still occurs when building the latest network-manager.
I also tried building our bluez snap with 2.43, and it appears normal (ie. it didn't increase in size). Next I built our previous release of the network-manager snap (1.2.2-15), and it also builds normally, so I think this problem is related to the changes made to the network-manager snap post 1.2.2-15.