* Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) [not found] ` <f12d07da-8692-5321-95e1-8b2fb5a84cf1@simark.ca> @ 2022-05-03 23:36 ` Mark Wielaard 2022-05-04 0:51 ` Simon Marchi 2022-06-15 7:33 ` Tom de Vries 0 siblings, 2 replies; 9+ messages in thread From: Mark Wielaard @ 2022-05-03 23:36 UTC (permalink / raw) To: Simon Marchi; +Cc: gdb-patches [-- Attachment #1: Type: text/plain, Size: 516 bytes --] Hi Simon, Moved to gdb-patches, now that we have an approach and concrete patch. On Tue, May 03, 2022 at 11:41:33AM -0400, Simon Marchi wrote: > If it's really just the diagnostic that is bogus, my preference would be > to try to silence the diagnostic and not modify the code. > > It would require adding a DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD to > include/diagnostics.h. > > I would also limit the disabling to just that arch OK, how about the attached? Build on fedora/s390x and debian/aarch64. Thanks, Mark [-- Attachment #2: 0001-gdb-Workaround-stringop-overread-warning-in-debuginf.patch --] [-- Type: text/x-diff, Size: 2485 bytes --] From 7ee5428d3bb06e5b4b8379a2a84092102a09a4ef Mon Sep 17 00:00:00 2001 From: Mark Wielaard <mark@klomp.org> Date: Tue, 3 May 2022 23:17:31 +0000 Subject: [PATCH] gdb: Workaround stringop-overread warning in debuginfod-support.c on s390x For some reason g++ 11.2.1 on s390x produces a spurious warning for stringop-overread in debuginfod_is_enabled for url_view. Add a new DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD macro to suppress this warning. include/ChangeLog: * diagnostics.h (DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD): New macro. gdb/ChangeLog: * debuginfod-support.c (debuginfod_is_enabled): Use DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD on s390x. --- gdb/debuginfod-support.c | 11 +++++++++++ include/diagnostics.h | 7 +++++++ 2 files changed, 18 insertions(+) diff --git a/gdb/debuginfod-support.c b/gdb/debuginfod-support.c index 4ce2e786..67e625db 100644 --- a/gdb/debuginfod-support.c +++ b/gdb/debuginfod-support.c @@ -17,6 +17,7 @@ along with this program. If not, see <http://www.gnu.org/licenses/>. */ #include "defs.h" +#include "diagnostics.h" #include <errno.h> #include "gdbsupport/scoped_fd.h" #include "debuginfod-support.h" @@ -191,7 +192,17 @@ debuginfod_is_enabled () if (off == gdb::string_view::npos) break; url_view = url_view.substr (off); +#if defined (__s390x__) + /* g++ 11.2.1 on s390x seems convinced url_view might be of + SIZE_MAX length. And so complains because the length of + an array can only be PTRDIFF_MAX. */ + DIAGNOSTIC_PUSH + DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD +#endif off = url_view.find_first_of (' '); +#if defined (__s390x__) + DIAGNOSTIC_POP +#endif gdb_printf (_(" <%ps>\n"), styled_string (file_name_style.style (), diff --git a/include/diagnostics.h b/include/diagnostics.h index f10d0661..8bf5a3c3 100644 --- a/include/diagnostics.h +++ b/include/diagnostics.h @@ -76,6 +76,9 @@ # define DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION \ DIAGNOSTIC_IGNORE ("-Wstringop-truncation") +# define DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD \ + DIAGNOSTIC_IGNORE ("-Wstringop-overread") + # define DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL \ DIAGNOSTIC_IGNORE ("-Wformat-nonliteral") @@ -108,6 +111,10 @@ # define DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION #endif +#ifndef DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD +# define DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD +#endif + #ifndef DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL # define DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL #endif -- 2.34.1 ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) 2022-05-03 23:36 ` gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) Mark Wielaard @ 2022-05-04 0:51 ` Simon Marchi 2022-06-15 7:33 ` Tom de Vries 1 sibling, 0 replies; 9+ messages in thread From: Simon Marchi @ 2022-05-04 0:51 UTC (permalink / raw) To: Mark Wielaard; +Cc: gdb-patches On 2022-05-03 19:36, Mark Wielaard wrote: > Hi Simon, > > Moved to gdb-patches, now that we have an approach and concrete patch. > > On Tue, May 03, 2022 at 11:41:33AM -0400, Simon Marchi wrote: >> If it's really just the diagnostic that is bogus, my preference would be >> to try to silence the diagnostic and not modify the code. >> >> It would require adding a DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD to >> include/diagnostics.h. >> >> I would also limit the disabling to just that arch > > OK, how about the attached? Build on fedora/s390x and debian/aarch64. > > Thanks, > > Mark Hi Mark, This is ok. Note that you don't need the ChangeLog entry for the GDB change, but you do for the include/ change. Simon ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) 2022-05-03 23:36 ` gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) Mark Wielaard 2022-05-04 0:51 ` Simon Marchi @ 2022-06-15 7:33 ` Tom de Vries 2022-06-15 11:09 ` Mark Wielaard 1 sibling, 1 reply; 9+ messages in thread From: Tom de Vries @ 2022-06-15 7:33 UTC (permalink / raw) To: Mark Wielaard, Simon Marchi; +Cc: gdb-patches On 5/4/22 01:36, Mark Wielaard wrote: > Hi Simon, > > Moved to gdb-patches, now that we have an approach and concrete patch. > > On Tue, May 03, 2022 at 11:41:33AM -0400, Simon Marchi wrote: >> If it's really just the diagnostic that is bogus, my preference would be >> to try to silence the diagnostic and not modify the code. >> >> It would require adding a DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD to >> include/diagnostics.h. >> >> I would also limit the disabling to just that arch > > OK, how about the attached? Build on fedora/s390x and debian/aarch64. > > diff --git a/include/diagnostics.h b/include/diagnostics.h > index f10d0661..8bf5a3c3 100644 > --- a/include/diagnostics.h > +++ b/include/diagnostics.h > @@ -76,6 +76,9 @@ > # define DIAGNOSTIC_IGNORE_STRINGOP_TRUNCATION \ > DIAGNOSTIC_IGNORE ("-Wstringop-truncation") > > +# define DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD \ > + DIAGNOSTIC_IGNORE ("-Wstringop-overread") > + > # define DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL \ > DIAGNOSTIC_IGNORE ("-Wformat-nonliteral") > This caused a build breaker (which I ran into once the warning suppression in debuginfod-support.c was enabled also for x86_64). Fixed here ( https://sourceware.org/pipermail/gdb-patches/2022-June/190097.html ). I did wonder why the builder didn't catch this. I found out that the buildbot gdb-opensuseleap-x86_64 did't fail because the buildbot builds gdb without debuginfod support. Mark, is this something we want to fix? For opensuse it's package libdebuginfod-devel. Thanks, - Tom ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) 2022-06-15 7:33 ` Tom de Vries @ 2022-06-15 11:09 ` Mark Wielaard 2022-06-15 14:38 ` Mark Wielaard 0 siblings, 1 reply; 9+ messages in thread From: Mark Wielaard @ 2022-06-15 11:09 UTC (permalink / raw) To: Tom de Vries, Simon Marchi; +Cc: gdb-patches, buildbot [-- Attachment #1: Type: text/plain, Size: 960 bytes --] Hi Tom, On Wed, 2022-06-15 at 09:33 +0200, Tom de Vries wrote: > This caused a build breaker (which I ran into once the warning > suppression in debuginfod-support.c was enabled also for x86_64). > > Fixed here ( > https://sourceware.org/pipermail/gdb-patches/2022-June/190097.html ). Apologies, I was sure I had tested everywhere, but clearly missed that on an older install I didn't have debuginfod installed. Thanks for fixing it. > I did wonder why the builder didn't catch this. I found out that > the > buildbot gdb-opensuseleap-x86_64 did't fail because the buildbot > builds > gdb without debuginfod support. > > Mark, is this something we want to fix? > > For opensuse it's package libdebuginfod-devel. Yep, that seems like a good idea. Should now be added to the opensuse- leap container. CC buildbot list, where you can propose such patches yourself if you notice anything else missing. Cheers, Mark [-- Attachment #2: Type: text/x-patch, Size: 1071 bytes --] From 1e59a7816e641fe0ae35dc971fad046dc3cb10f9 Mon Sep 17 00:00:00 2001 From: Mark Wielaard <mark@klomp.org> Date: Wed, 15 Jun 2022 13:04:15 +0200 Subject: [PATCH] Containerfile-opensuse-leap: Add libdebuginfod-devel --- builder/containers/Containerfile-opensuse-leap | 1 + 1 file changed, 1 insertion(+) diff --git a/builder/containers/Containerfile-opensuse-leap b/builder/containers/Containerfile-opensuse-leap index ecfa0d3..77f94d5 100644 --- a/builder/containers/Containerfile-opensuse-leap +++ b/builder/containers/Containerfile-opensuse-leap @@ -9,6 +9,7 @@ RUN zypper -n install \ bzip2 libbz2-devel xz xz-devel gzip zlib-devel zstd libzstd-devel \ findutils file tar curl libarchive-devel libcurl-devel \ libmicrohttpd-devel sqlite-devel libelf-devel libdw-devel \ + libdebuginfod-devel \ xmlto poppler-tools libxslt docbook-dtds docbook-xsl-stylesheets \ libxml2-devel dos2unix dpkg python3-devel python3-mock \ python3-rpm python3-pyxdg python3-pip openmpi-devel gdb help2man wget \ -- 2.18.4 ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) 2022-06-15 11:09 ` Mark Wielaard @ 2022-06-15 14:38 ` Mark Wielaard 2022-06-15 19:18 ` Martin Liška 0 siblings, 1 reply; 9+ messages in thread From: Mark Wielaard @ 2022-06-15 14:38 UTC (permalink / raw) To: Tom de Vries, Simon Marchi; +Cc: gdb-patches, buildbot Hi Tom, On Wed, 2022-06-15 at 13:09 +0200, Mark Wielaard wrote: > > I did wonder why the builder didn't catch this. I found out that > > the > > buildbot gdb-opensuseleap-x86_64 did't fail because the buildbot > > builds > > gdb without debuginfod support. > > > > Mark, is this something we want to fix? > > > > For opensuse it's package libdebuginfod-devel. > > Yep, that seems like a good idea. Should now be added to the > opensuse- > leap container. Note that this didn't actually work. Although the package is now installed: builder@df808da35762:~/build> rpm -qa | grep debuginfod libdebuginfod-devel-0.185-150400.3.35.x86_64 The configure test still fails: configure:7009: checking whether to use debuginfod configure:7011: result: auto configure:7017: checking for libdebuginfod >= 0.179 configure:7024: $PKG_CONFIG --exists --print-errors "libdebuginfod >= 0.179" configure:7027: $? = 0 configure:7041: $PKG_CONFIG --exists --print-errors "libdebuginfod >= 0.179" configure:7044: $? = 0 configure:7069: gcc -o conftest -g -O2 -ldebuginfod conftest.c -ldl >&5 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -ldebuginfod collect2: error: ld returned 1 exit status The problem is: builder@df808da35762:~/build> ls -lah /usr/lib64/libdebuginfod.so lrwxrwxrwx 1 root root 22 May 7 23:06 /usr/lib64/libdebuginfod.so -> libdebuginfod-0.185.so builder@df808da35762:~/build> ls -lah /usr/lib64/libdebuginfod-0.185.so ls: cannot access '/usr/lib64/libdebuginfod-0.185.so': No such file or directory Is that a opensuse leap packaging bug? BTW. To debug such builder container issues you can use this IMHO handy guide: https://sourceware.org/git/?p=builder.git;a=blob;f=README_containers;hb=HEAD > CC buildbot list, where you can propose such patches yourself if you > notice anything else missing. > > Cheers, > > Mark > ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) 2022-06-15 14:38 ` Mark Wielaard @ 2022-06-15 19:18 ` Martin Liška 2022-06-15 19:48 ` Mark Wielaard 0 siblings, 1 reply; 9+ messages in thread From: Martin Liška @ 2022-06-15 19:18 UTC (permalink / raw) To: Mark Wielaard, Tom de Vries, Simon Marchi; +Cc: buildbot, gdb-patches On 6/15/22 16:38, Mark Wielaard wrote: > Hi Tom, > > On Wed, 2022-06-15 at 13:09 +0200, Mark Wielaard wrote: >>> I did wonder why the builder didn't catch this. I found out that >>> the >>> buildbot gdb-opensuseleap-x86_64 did't fail because the buildbot >>> builds >>> gdb without debuginfod support. >>> >>> Mark, is this something we want to fix? >>> >>> For opensuse it's package libdebuginfod-devel. >> >> Yep, that seems like a good idea. Should now be added to the >> opensuse- >> leap container. > > Note that this didn't actually work. Although the package is now > installed: > > builder@df808da35762:~/build> rpm -qa | grep debuginfod > libdebuginfod-devel-0.185-150400.3.35.x86_64 > > The configure test still fails: > > configure:7009: checking whether to use debuginfod > configure:7011: result: auto > configure:7017: checking for libdebuginfod >= 0.179 > configure:7024: $PKG_CONFIG --exists --print-errors "libdebuginfod >= 0.179" > configure:7027: $? = 0 > configure:7041: $PKG_CONFIG --exists --print-errors "libdebuginfod >= 0.179" > configure:7044: $? = 0 > configure:7069: gcc -o conftest -g -O2 -ldebuginfod conftest.c -ldl >&5 > /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -ldebuginfod > collect2: error: ld returned 1 exit status > > The problem is: > > builder@df808da35762:~/build> ls -lah /usr/lib64/libdebuginfod.so > lrwxrwxrwx 1 root root 22 May 7 23:06 /usr/lib64/libdebuginfod.so -> > libdebuginfod-0.185.so > builder@df808da35762:~/build> ls -lah /usr/lib64/libdebuginfod-0.185.so > ls: cannot access '/usr/lib64/libdebuginfod-0.185.so': No such file or > directory > > Is that a opensuse leap packaging bug? Note we don't have the package in Leap and this is what I see when building the current Containerfile-opensuse-leap: STEP 3/10: RUN zypper -n install gcc gcc-c++ libtool ccache valgrind isl-devel mpc-devel mpfr-devel gmp-devel patch util-linux diffutils iproute2 bsdtar cpio procps coreutils make git autoconf dejagnu automake gettext-devel bison flex bzip2 libbz2-devel xz xz-devel gzip zlib-devel zstd libzstd-devel findutils file tar curl libarchive-devel libcurl-devel libmicrohttpd-devel sqlite-devel libelf-devel libdw-devel libdebuginfod-devel xmlto poppler-tools libxslt docbook-dtds docbook-xsl-stylesheets libxml2-devel dos2unix dpkg python3-devel python3-mock python3-rpm python3-pyxdg python3-pip openmpi-devel gdb help2man wget texinfo libexpat-devel glibc-devel glibc-locale ... 'libdebuginfod-devel' not found in package names. Trying capabilities. No provider of 'libdebuginfod-devel' found. ['--plus-content debug'?] Martin > > BTW. To debug such builder container issues you can use this IMHO handy > guide: > https://sourceware.org/git/?p=builder.git;a=blob;f=README_containers;hb=HEAD > >> CC buildbot list, where you can propose such patches yourself if you >> notice anything else missing. >> >> Cheers, >> >> Mark >> ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) 2022-06-15 19:18 ` Martin Liška @ 2022-06-15 19:48 ` Mark Wielaard 2022-06-16 4:09 ` Martin Liška 0 siblings, 1 reply; 9+ messages in thread From: Mark Wielaard @ 2022-06-15 19:48 UTC (permalink / raw) To: Martin Liška; +Cc: Tom de Vries, Simon Marchi, buildbot, gdb-patches Hi Martin, On Wed, Jun 15, 2022 at 09:18:38PM +0200, Martin Liška wrote: > > Is that a opensuse leap packaging bug? > > Note we don't have the package in Leap and this is what I see when building the current Containerfile-opensuse-leap: > > STEP 3/10: RUN zypper -n install gcc gcc-c++ libtool ccache valgrind isl-devel mpc-devel mpfr-devel gmp-devel patch util-linux diffutils iproute2 bsdtar cpio procps coreutils make git autoconf dejagnu automake gettext-devel bison flex bzip2 libbz2-devel xz xz-devel gzip zlib-devel zstd libzstd-devel findutils file tar curl libarchive-devel libcurl-devel libmicrohttpd-devel sqlite-devel libelf-devel libdw-devel libdebuginfod-devel xmlto poppler-tools libxslt docbook-dtds docbook-xsl-stylesheets libxml2-devel dos2unix dpkg python3-devel python3-mock python3-rpm python3-pyxdg python3-pip openmpi-devel gdb help2man wget texinfo libexpat-devel glibc-devel glibc-locale > ... > 'libdebuginfod-devel' not found in package names. Trying capabilities. > No provider of 'libdebuginfod-devel' found. ['--plus-content debug'?] That is surprising, I did test locally before adding the package. And clearly the buildbot/docker builder could find the package and build the image. And when I do it locally it also seems to work: $ podman build -t builder-opensuse-leap -f builder/containers/Containerfile-opensuse-leap builder/containers [...] Retrieving package libdebuginfod-devel-0.185-150400.3.35.x86_64 (129/429), 23.4 KiB ( 8.9 KiB unpacked) Retrieving: libdebuginfod-devel-0.185-150400.3.35.x86_64.rpm [done] [...] (129/429) Installing: libdebuginfod-devel-0.185-150400.3.35.x86_64 [.......done] [...] Successfully tagged localhost/builder-opensuse-leap:latest 395a607b4cd69683b3212862d3dd3c8557b2a581f210cb903c1168ecd5f01b16 $ podman run --name opensuse-leap -ti --entrypoint /bin/bash builder-opensuse-leap builder@9d1600f0c01e:~> rpm -q libdebuginfod-devel libdebuginfod-devel-0.185-150400.3.35.x86_64 Are the container files pulling from the wrong repositories? > > BTW. To debug such builder container issues you can use this IMHO handy > > guide: > > https://sourceware.org/git/?p=builder.git;a=blob;f=README_containers;hb=HEAD > > > >> CC buildbot list, where you can propose such patches yourself if you > >> notice anything else missing. > >> > >> Cheers, > >> > >> Mark ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) 2022-06-15 19:48 ` Mark Wielaard @ 2022-06-16 4:09 ` Martin Liška 2022-06-16 21:19 ` Mark Wielaard 0 siblings, 1 reply; 9+ messages in thread From: Martin Liška @ 2022-06-16 4:09 UTC (permalink / raw) To: Mark Wielaard; +Cc: Simon Marchi, buildbot, Tom de Vries, gdb-patches On 6/15/22 21:48, Mark Wielaard wrote: > $ podman run --name opensuse-leap -ti --entrypoint /bin/bash builder-opensuse-leap > builder@9d1600f0c01e:~> rpm -q libdebuginfod-devel > libdebuginfod-devel-0.185-150400.3.35.x86_64 > > Are the container files pulling from the wrong repositories? Yeah, I was still using 15.3, while we released 15.4 in the meantime. Apparently the following helps: podman build ... --pull=true And about: ls -lah /usr/lib64/libdebuginfod-0.185.so ls: cannot access '/usr/lib64/libdebuginfod-0.185.so': No such file or directory It's really a broken package and I'm going to fix it (it's missing Requires: libdebuginfod1 = %{version} In the meantime I install it manually in this podman file. Cheers, Martin ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) 2022-06-16 4:09 ` Martin Liška @ 2022-06-16 21:19 ` Mark Wielaard 0 siblings, 0 replies; 9+ messages in thread From: Mark Wielaard @ 2022-06-16 21:19 UTC (permalink / raw) To: Martin Liška; +Cc: Simon Marchi, buildbot, Tom de Vries, gdb-patches [-- Attachment #1: Type: text/plain, Size: 1190 bytes --] Hi Martin, On Thu, Jun 16, 2022 at 06:09:13AM +0200, Martin Liška wrote: > > $ podman run --name opensuse-leap -ti --entrypoint /bin/bash builder-opensuse-leap > > builder@9d1600f0c01e:~> rpm -q libdebuginfod-devel > > libdebuginfod-devel-0.185-150400.3.35.x86_64 > > > > Are the container files pulling from the wrong repositories? > > Yeah, I was still using 15.3, while we released 15.4 in the meantime. > Apparently the following helps: > > podman build ... --pull=true Aha. The reason this wasn't necessary on the container builders was because they do a docker system prune -a -f every Sunday to get a fresh image. Note that this did also cause libabigail to turn green on opensuse leap (because it got a newer elfutils): https://sourceware.org/pipermail/libabigail/2022q2/004430.html > And about: > > ls -lah /usr/lib64/libdebuginfod-0.185.so > ls: cannot access '/usr/lib64/libdebuginfod-0.185.so': No such file or > directory > > It's really a broken package and I'm going to fix it (it's missing > Requires: libdebuginfod1 = %{version} > > In the meantime I install it manually in this podman file. Thanks! I'll add this to the README_containers. Cheers, Mark [-- Attachment #2: 0001-README_containers-Document-build-pull-and-system-pru.patch --] [-- Type: text/x-diff, Size: 1819 bytes --] From 530d374997b18b46965de4c93e86543e1d2b89f5 Mon Sep 17 00:00:00 2001 From: Mark Wielaard <mark@klomp.org> Date: Thu, 16 Jun 2022 23:18:43 +0200 Subject: [PATCH] README_containers: Document build --pull and system prune -a -f --- README_containers | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/README_containers b/README_containers index 66ac558..c414f72 100644 --- a/README_containers +++ b/README_containers @@ -69,8 +69,9 @@ Building the image ------------------ Note that the container files are rebuild once a week for the -builder.sourceware.org workers. So although unlikely it might be that -a freshly build container contains slightly newer versions of the +builder.sourceware.org workers (each Sunday the container builders run +docker system prune -a -f). So although unlikely it might be that a +freshly build container contains slightly newer versions of the packages than the one that ran on the builder.sourceware.org worker. The containers contain all build dependencies for all projects @@ -85,6 +86,10 @@ podman build -t builder-debian-stable \ -f builder/containers/Containerfile-debian-stable \ builder/containers +If you want to make sure you get the latest base image add --pull +which will attempt to pull a newer version of the image even if you +already got one locally. + Or use docker instead of podman, they take the same arguments (although the last PATH is optional in some versions). @@ -109,4 +114,7 @@ container and enter it as root: podman start debian-stable podman exec -it --user root debian-stable apt install emacs +After you are done you can reclaim all disk space used by the images +and containers by running: podman system prune -a -f + The same works with the docker command. -- 2.30.2 ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2022-06-16 21:19 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <YmbmguMq2Aq+BzAX@wildebeest.org> [not found] ` <524b04b7-a78c-7aae-4605-b40f61e6830c@arm.com> [not found] ` <YmhzY4c3pOPLRgSw@wildebeest.org> [not found] ` <16fe426d-c436-f030-dc43-0e81e7f0e853@arm.com> [not found] ` <20220428141957.GB23335@gnu.wildebeest.org> [not found] ` <m3zgk5clif.fsf@fitzsim.org> [not found] ` <20220428162803.GD23335@gnu.wildebeest.org> [not found] ` <20220429200422.GB7305@gnu.wildebeest.org> [not found] ` <20220501194445.GB30898@gnu.wildebeest.org> [not found] ` <f12d07da-8692-5321-95e1-8b2fb5a84cf1@simark.ca> 2022-05-03 23:36 ` gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) Mark Wielaard 2022-05-04 0:51 ` Simon Marchi 2022-06-15 7:33 ` Tom de Vries 2022-06-15 11:09 ` Mark Wielaard 2022-06-15 14:38 ` Mark Wielaard 2022-06-15 19:18 ` Martin Liška 2022-06-15 19:48 ` Mark Wielaard 2022-06-16 4:09 ` Martin Liška 2022-06-16 21:19 ` Mark Wielaard
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).