Fair enough. Thanks for the detailed explanation!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851233
Title:
building a snap from the eoan tree using the raspi2 defconfig results
in gigantic
the included snapcraft.yaml means i need to have the whole tree locally
on disk, as someone who maintains a ton of community images for
UbuntuCore i prefer to just have the snapcraft.yaml locally so the disk
is only cluttered during build. along with that i am trying to build the
eoan tree for the
What's wrong with using the provided/included snapcraft.yaml?
So can this case be closed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851233
Title:
building a snap from the eoan tree using the
well, as a user/customer building my own kernel i'd kind of expect the
defconfig for a flavour to not be a debug config.
but indeed you are correct, i should have taken a look at the included
snapcraft.yaml which, despite being for the wrong flavour (generic/pc-
kernel), indeed contains
DEBUG_INFO=y is perfectly fine and required. We build all the blobs with
debug info and then strip them for the 'regular' kernel wo/ debug
symbols.
Potentially relevant: https://bugs.launchpad.net/ubuntu/+source/linux-
raspi2/+bug/1851469
DEBUG_INFO *needs* to be overridden in any snapcraft.yaml
For eoan, I inherited "DEBUG_INFO=y" from disco raspi2 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851233
Title:
building a snap from the eoan tree using the raspi2 defconfig results
ok, this looks a bit more reasonable now ...
$ ls -lh pi4-kernel_raspi2-5.3.0-1011.12_armhf.snap
-rw-r--r-- 1 ogra ogra 211M Nov 4 17:05
pi4-kernel_raspi2-5.3.0-1011.12_armhf.snap
so CONFIG_DEBUG_INFO=y should better be turned off by default for people
building snaps from our trees ;)
--
yup, seems this is (surprisingly) on by default ...
$ grep DEBUG_INFO parts/kernel/build/.config
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_INFO_REDUCED is not set
# CONFIG_DEBUG_INFO_SPLIT is not set
CONFIG_DEBUG_INFO_DWARF4=y
# CONFIG_DEBUG_INFO_BTF is not set
i'll try a re-build and override that
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851233
Title:
building a snap from the eoan tree using the
I am wondering if CONFIG_DEBUG_INFO is turned on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851233
Title:
building a snap from the eoan tree using the raspi2 defconfig results
in gigantic
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851233
Title:
building a snap from the eoan tree using the raspi2 defconfig
i also tried using the "source-branch: raspi2" argument in the
snapcraft.yaml instead of using teh master branch and the "source-tag:"
option, but this results in the same big size ...
additionally i'd like to remark that due to the transactional nature of
UbuntuCore we need to keep the kernel
12 matches
Mail list logo
