From: Valentin Vidic <vvidic@debian.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [ClusterLabs] gfs2-utils 3.5.0 released
Date: Tue, 14 Feb 2023 21:17:58 +0100 [thread overview]
Message-ID: <Y+vsdnFHPJifPzE/@valentin-vidic.from.hr> (raw)
In-Reply-To: <417a9b47-f893-2a9e-25f1-bb7e9feb20e2@redhat.com>
On Tue, Feb 14, 2023 at 06:18:55AM +0100, Fabio M. Di Nitto wrote:
> The process would have to look like:
>
> <deploy amd64 debian image and add to CI> (usual)
> apt-get install <list of packages + 32 bit versions of them>
> git clone gfs2-utils
> export CFLAGS/LDFLAGS/CC or whatever env var
> <normal build bits go here>
> ./autogen.sh
> ./configure..
> make
> make <tests>
>
> Using other build tools like debbuild or mock has been problematic in the
> past for other projects, might not be the case for gfs2-utils.
>
> so you can try that all in a local VM and let me know the steps, then we can
> add it to CI.
Sure, the commands to build and test a 32-bit version look like this for me:
dpkg --add-architecture i386
apt-get update
apt-get install --yes build-essential crossbuild-essential-i386 autoconf automake autopoint autotools-dev bison flex check:i386 libblkid-dev:i386 libbz2-dev:i386 libncurses-dev:i386 libtool pkg-config:i386 zlib1g-dev:i386
./configure --build=x86_64-linux-gnu --host=i686-linux-gnu
make
make check
--
Valentin
next prev parent reply other threads:[~2023-02-14 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 13:12 [Cluster-devel] gfs2-utils 3.5.0 released Andrew Price
2023-02-11 17:16 ` [Cluster-devel] [ClusterLabs] " Valentin Vidić
2023-02-13 9:58 ` Andrew Price
2023-02-13 16:54 ` Andrew Price
2023-02-13 23:52 ` Valentin Vidic
2023-02-14 5:18 ` Fabio M. Di Nitto
2023-02-14 20:17 ` Valentin Vidic [this message]
2023-02-15 4:55 ` Fabio M. Di Nitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+vsdnFHPJifPzE/@valentin-vidic.from.hr \
--to=vvidic@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).