From: Aldrin <akmontan@ucsc.edu>
To: users@dpdk.org
Subject: Re: Struggling with meson in dpdk 21.11
Date: Tue, 17 Sep 2024 13:21:04 -0700 [thread overview]
Message-ID: <CAC-Ect-c=iZ17Y3_TDiKnawAThOB-L89KBfj1cmEZttgn0jv=w@mail.gmail.com> (raw)
In-Reply-To: <CAC-Ect-SeEoHarX6JxwEtQth2kGfYRU1a5PgKv1qoCV7E-X1kw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2525 bytes --]
Actually, I misunderstood destdir and some of the other context, my
apologies.
I do think that it makes more sense to use "x86_64-native-linux-gcc" as a
prefix and "/opt/intel/dpdk-stable-21.11.7" as a destdir, but that seems
unlikely to solve the problem.
maybe you can redirect the output of compilation to a log file and share
its output?
On Tue, Sep 17, 2024 at 12:40 PM Aldrin <akmontan@ucsc.edu> wrote:
> > > $ cd /opt/intel/dpdk-stable-21.11.7
> > > $ sudo meson -Dexamples=all -Dprefix="/"
> > >
> -Ddisable_drivers=common/mvep,common/mlx5,net/mvneta,net/mvpp2,net/nfb,net/mlx4,net/mlx5,\
> > >
> crypto/qat,crypto/aesni_gcm,crypto/aesni_mb,crypto/armv8,crypto/ccp,crypto/kasumi,crypto/mvsam,crypto/openssl,\
> > >
> crypto/snow3g,crypto/zuc,compress/isal,regex/mlx5,vdpa/mlx5,net/pcap,net/szedata2,raw/ifpga,net/af_xdp,net/ipn3ke,\
> > > crypto/ipsec_mb,crypto/ipsec_mb,crypto/mlx5,compress/mlx5,gpu/cuda
> build
> > > $ cd build
> > > $ sudo ninja
>
> > Don't build as root. Use:
> > $ ninja -C build
>
> I'm not sure this will address the issue, but you should avoid doing most
> of these things as root.
>
> `export INSTALL_PREFIX="/x86_64-native-linux-gcc"`
> `meson setup build`
> `meson configure -Dexamples=all \
> -Dprefix="${INSTALL_PREFIX}" \
> -Ddisable_drivers=common/mvep,common/mlx5,net/mvneta,
> net/mvpp2,net/nfb,net/mlx4,net/mlx5,crypto/qat,crypto/aesni_gcm,crypto/aesni_mb,crypto/armv8,crypto/ccp,crypto/kasumi,crypto/mvsam,crypto/openssl,crypto/snow3g,crypto/zuc,compress/isal,regex/mlx5,vdpa/mlx5,net/pcap,net/szedata2,raw/ifpga,net/af_xdp,net/ipn3ke,crypto/ipsec_mb,crypto/ipsec_mb,crypto/mlx5,compress/mlx5,gpu/cuda
> \
> build`
> `meson compile -C build`
> `meson install -C build`
>
> where I do notice that you're setting some conflicting options is that you
> have `-Dprefix="/"` when configuring and you also have
> `--destdir=../x86_64-native-linux-gcc` when installing. I'm not sure why
> you would set these to different paths unless you're essentially on a
> root-only system and you are doing everything from the root directory?
>
> In my example above, I set a variable, INSTALL_PREFIX, and use that in the
> configure step instead. Then, when you install, just let it install to the
> prefix that you specified. Presumably, this will ensure that all paths are
> correct whereas setting a different destdir from the prefix could
> potentially mismatch some paths.
>
>
[-- Attachment #2: Type: text/html, Size: 4220 bytes --]
next prev parent reply other threads:[~2024-09-17 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3759.1726527514.951.users@dpdk.org>
2024-09-17 19:40 ` Aldrin
2024-09-17 20:21 ` Aldrin [this message]
2024-09-19 15:44 ` David Aldrich
2024-09-16 17:42 David Aldrich
2024-09-16 19:19 ` Stephen Hemminger
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='CAC-Ect-c=iZ17Y3_TDiKnawAThOB-L89KBfj1cmEZttgn0jv=w@mail.gmail.com' \
--to=akmontan@ucsc.edu \
--cc=users@dpdk.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).