From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <users-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id EB2E5459B6
	for <public@inbox.dpdk.org>; Tue, 17 Sep 2024 21:40:32 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 9D9B540608;
	Tue, 17 Sep 2024 21:40:32 +0200 (CEST)
Received: from mail-vs1-f41.google.com (mail-vs1-f41.google.com
 [209.85.217.41]) by mails.dpdk.org (Postfix) with ESMTP id DE52340280
 for <users@dpdk.org>; Tue, 17 Sep 2024 21:40:30 +0200 (CEST)
Received: by mail-vs1-f41.google.com with SMTP id
 ada2fe7eead31-49bcd253360so212173137.2
 for <users@dpdk.org>; Tue, 17 Sep 2024 12:40:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=ucsc.edu; s=ucsc-google-2018; t=1726602030; x=1727206830; darn=dpdk.org;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :from:to:cc:subject:date:message-id:reply-to;
 bh=JkWHXoWwzfpgG/HqTyCDRz9/cf1DyssYURol1m/wNpQ=;
 b=HBnYmeysOHh0gSG9LfxFREa752lMDzbZSNfdBt8uQ1sKJA/7Ob+bt/vgq8XhfBFM5c
 AqECzYjXFK/VhLQsCEMU5ezB2IRct4kgLQxVbs854Ae/CTqCtVD0HHYS6UKJsLdZyQlT
 a2+92JpWM9hUoIt3Xo2Vu8MkmhS35MyRYC9r+MkJwpP3FsoxcIzBnR1IKcCgw3oU0h0S
 xc3MgI7XDBYG5Ga4KvZ2iMFnqgFnOnHmKH2bk9+wdR/SNbnzcgabEXyTj1kOOzMLgqlb
 TigOyK09kclteDih9q/UfQWtGskxFZvv9/hA5YWNjU3hL2+IRGusj+RlmXl59h6DaqAl
 fgUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1726602030; x=1727206830;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
 bh=JkWHXoWwzfpgG/HqTyCDRz9/cf1DyssYURol1m/wNpQ=;
 b=XaSiuo3dQS5lrf/HihZBeDo22rKcYawBnnb4lAwrIhUOSevF8KjbQBMMBRqEU0jOfK
 pdw55BO/fsRGyJkwLgWhF0RCrNiJvffLtNkv9OKGFq6waZxnBxFDXtBmBmI5MeXqviHw
 OJvCDOqArsGrPlDXyiYe8rtoOMoNzsGH/Bfgow1G2/V1vVUIqmpZXdQ8iU6EbeTv6Mk0
 B19sk0tu8LEwgezF+aTea+Q+Fpy4w1BZt98OOzfUG0Lt0BzW4A7fNycp0F/y2o05n36P
 Z403LFDJzItIGhRt7UJZNk2TZLFmxIAntJK198fmqbj7NKOkMxdayURd85gYFdPG7R/T
 v+UQ==
X-Gm-Message-State: AOJu0YxdQVF0w1e/rxWPsbEujlGmlqqF3DXrnmTcz4e0XqbwUc+pi5Le
 tRjVoZlbuWhusu6ct2VB7InxZ7/LKY6NJeBOYK9EPXMDKpx3C9zrXZdqZ9PDn4X3SNUEfXmHVZ8
 SVkWfvAP5LSSdke9ejkVDjJLpvOtZ7crIg3+EF4CR/A/lwUKtwfM=
X-Google-Smtp-Source: AGHT+IGHF8zPZv4UxIP1iH+i4YU7FXfhbgJc43z/U675CnFGctPQ0v7YCH42AsN1aO2IIECxEEs7mJYFZIfgHWj6++A=
X-Received: by 2002:a05:6102:c04:b0:49b:d6d9:4aa2 with SMTP id
 ada2fe7eead31-49d4157d11fmr6950200137.3.1726602029902; Tue, 17 Sep 2024
 12:40:29 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.3759.1726527514.951.users@dpdk.org>
In-Reply-To: <mailman.3759.1726527514.951.users@dpdk.org>
From: Aldrin <akmontan@ucsc.edu>
Date: Tue, 17 Sep 2024 12:40:18 -0700
Message-ID: <CAC-Ect-SeEoHarX6JxwEtQth2kGfYRU1a5PgKv1qoCV7E-X1kw@mail.gmail.com>
Subject: Re: Struggling with meson in dpdk 21.11
To: users@dpdk.org
Content-Type: multipart/alternative; boundary="000000000000a94fb5062255dc4f"
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
Errors-To: users-bounces@dpdk.org

--000000000000a94fb5062255dc4f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> > $ cd /opt/intel/dpdk-stable-21.11.7
> > $ sudo meson -Dexamples=3Dall -Dprefix=3D"/"
> >
-Ddisable_drivers=3Dcommon/mvep,common/mlx5,net/mvneta,net/mvpp2,net/nfb,ne=
t/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/sz=
edata2,raw/ifpga,net/af_xdp,net/ipn3ke,\
> > crypto/ipsec_mb,crypto/ipsec_mb,crypto/mlx5,compress/mlx5,gpu/cuda buil=
d
> > $ 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=3D"/x86_64-native-linux-gcc"`
`meson setup build`
`meson configure -Dexamples=3Dall \
                 -Dprefix=3D"${INSTALL_PREFIX}"   \
                 -Ddisable_drivers=3Dcommon/mvep,common/mlx5,net/mvneta,
net/mvpp2,net/nfb,net/mlx4,net/mlx5,crypto/qat,crypto/aesni_gcm,crypto/aesn=
i_mb,crypto/armv8,crypto/ccp,crypto/kasumi,crypto/mvsam,crypto/openssl,cryp=
to/snow3g,crypto/zuc,compress/isal,regex/mlx5,vdpa/mlx5,net/pcap,net/szedat=
a2,raw/ifpga,net/af_xdp,net/ipn3ke,crypto/ipsec_mb,crypto/ipsec_mb,crypto/m=
lx5,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=3D"/"` when configuring and you also have
`--destdir=3D../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.

--000000000000a94fb5062255dc4f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">&gt; &gt; $ cd /opt/intel/dpdk-stable-21.=
11.7<br>&gt; &gt; $ sudo meson -Dexamples=3Dall -Dprefix=3D&quot;/&quot;<br=
>
&gt; &gt; -Ddisable_drivers=3Dcommon/mvep,common/mlx5,net/mvneta,net/mvpp2,=
net/nfb,net/mlx4,net/mlx5,\<br>&gt;=20
&gt; crypto/qat,crypto/aesni_gcm,crypto/aesni_mb,crypto/armv8,crypto/ccp,cr=
ypto/kasumi,crypto/mvsam,crypto/openssl,\<br>&gt;=20
&gt; crypto/snow3g,crypto/zuc,compress/isal,regex/mlx5,vdpa/mlx5,net/pcap,n=
et/szedata2,raw/ifpga,net/af_xdp,net/ipn3ke,\<br>&gt;=20
&gt; crypto/ipsec_mb,crypto/ipsec_mb,crypto/mlx5,compress/mlx5,gpu/cuda bui=
ld<br>&gt;=20
&gt; $ cd build<br>&gt;=20
&gt; $ sudo ninja<br>
<br>&gt;=20
Don&#39;t build as root. Use:<br>&gt;=C2=A0 $ ninja -C build<div><div dir=
=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><=
div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div><br></div><div>I&#39;m=
 not sure this will address the issue, but you should avoid doing most of t=
hese things as root.</div><div><br></div><div><span style=3D"font-family:mo=
nospace">`export INSTALL_PREFIX=3D&quot;/x86_64-native-linux-gcc&quot;`</sp=
an><br></div><div><span style=3D"font-family:monospace">`meson setup build`=
</span></div><div><span style=3D"font-family:monospace">`meson configure -D=
examples=3Dall \</span></div><div><span style=3D"font-family:monospace">=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 -Dprefix=3D&quot;${INSTALL_PREFIX}&quot;=C2=A0=C2=A0 \<b=
r>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 -Ddisable_drivers=3Dcommon/mvep,</span><span style=
=3D"font-family:monospace">common/mlx5,</span><span style=3D"font-family:mo=
nospace"></span><span style=3D"font-family:monospace">net/mvneta,</span><sp=
an style=3D"font-family:monospace"></span><span style=3D"font-family:monosp=
ace">net/mvpp2,</span><span style=3D"font-family:monospace"></span><span st=
yle=3D"font-family:monospace">net/nfb,net/mlx4,net/mlx5,crypto/qat,crypto/a=
esni_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,cryp=
to/ipsec_mb,crypto/mlx5,compress/mlx5,gpu/cuda \</span></div><div><span sty=
le=3D"font-family:monospace">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 build`</span></div><div=
><span style=3D"font-family:monospace">`meson compile -C build`</span></div=
><div><span style=3D"font-family:monospace">`meson install -C build`<br></s=
pan></div><div><span style=3D"font-family:monospace"><br></span></div><div>=
<span style=3D"font-family:arial,sans-serif">where I do notice that you&#39=
;re setting some conflicting options is that you have `-Dprefix=3D&quot;/&q=
uot;` when configuring and you also have `--destdir=3D../x86_64-native-linu=
x-gcc` when installing. I&#39;m not sure why you would set these to differe=
nt paths unless you&#39;re essentially on a root-only system and you are do=
ing everything from the root directory?</span></div><div><span style=3D"fon=
t-family:arial,sans-serif"><br></span></div><div><span style=3D"font-family=
:arial,sans-serif">In my example above, I set a variable, INSTALL_PREFIX, a=
nd 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 pre=
fix could potentially mismatch some paths.</span></div><div><span style=3D"=
font-family:arial,sans-serif"><br></span></div></div></div></div></div></di=
v></div></div></div></div></div></div></div>

--000000000000a94fb5062255dc4f--