From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 44BF8A04BB; Tue, 6 Oct 2020 16:35:28 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 33C771B69F; Tue, 6 Oct 2020 16:35:26 +0200 (CEST) Received: from mail-oi1-f196.google.com (mail-oi1-f196.google.com [209.85.167.196]) by dpdk.org (Postfix) with ESMTP id ABB4B2952 for ; Tue, 6 Oct 2020 16:35:24 +0200 (CEST) Received: by mail-oi1-f196.google.com with SMTP id m7so12821934oie.0 for ; Tue, 06 Oct 2020 07:35:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KAirBXt3uFxhPWjlbXDzfkyOFC43UPSSKJ/R0xJQG94=; b=WFwEWq3PhaBIxDyUMX9LEjmlIEsRAHiml8FxS7aWey1i6L/0kfvfSLj3hMb4jUnVjd oL6QL7rBtsSNf2PM4YNqJX4kK9nqBEMagA8YBXx4AVCGm9Wj8mz+gVNNXWo9FrlLKBoE 1OoFUwyi1mwB+PGq2s5k7+us69TIYWV74watw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KAirBXt3uFxhPWjlbXDzfkyOFC43UPSSKJ/R0xJQG94=; b=cNork/Pql5rWHmiRpEisBQpEX9R1kpucBPmUsaPmZHMlREhwXJ4XB0pv1BBNLvMX0z 6M+0YD+95W2yyl8/MDxLkLJY0boLNzkVTKfrASuyswTbJZnCieD0pd960Zi3XYO7XGlN wUYlda4yefLw/mX5P9RwIc3YjXYUs7zaMZA4uD6M91QCrPW1S94q3DYtSkqgXVsEtFn5 2Llv4ZA3ZeUQ+4rUrgtubT87NMM8qDmyCl8OT5Ylq2i0cYd3W1fA4Ie93DQLxQa/t3Vi mm9bGxjIkiCUg/0g1gxDQOYp6lUKjaiNQrs5NsLNjQcfj1S+Qv3ESm7imMGQkcjNYXBO gICg== X-Gm-Message-State: AOAM533awwfpJbZz188dYSVm37bSb3rm2eI+qDTJUlymC/pgCbGlyz59 OohMHbXgbEJKJHgcCoxW8rjGNnA7AX80AYMHksZe4XwkoC9/8A== X-Google-Smtp-Source: ABdhPJxUD2p9IrsIutzMU9iABRuovnRWeIJVEWW7mbkpDNg+G9i9ROHujVuQOUxot7R/2HIuY+26QGaCmeX4tfmezhw= X-Received: by 2002:aca:6543:: with SMTP id j3mr3015957oiw.81.1601994923774; Tue, 06 Oct 2020 07:35:23 -0700 (PDT) MIME-Version: 1.0 References: <20200924163742.321600-1-lance.richardson@broadcom.com> <20200925091341.GB923@bricha3-MOBL.ger.corp.intel.com> <18414568.0SzrnlinNP@thomas> In-Reply-To: <18414568.0SzrnlinNP@thomas> From: Lance Richardson Date: Tue, 6 Oct 2020 10:35:13 -0400 Message-ID: To: Thomas Monjalon Cc: Bruce Richardson , dev@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH] build: support i686 target on x86 64-bit hosts X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, Oct 6, 2020 at 4:30 AM Thomas Monjalon wrote: > > 25/09/2020 15:27, Lance Richardson: > > Bruce Richardson wrote: > > > On Thu, Sep 24, 2020 at 12:37:42PM -0400, Lance Richardson wrote: > > > > Add meson cross files for building i686 targets using gcc on x86_64 > > > > linux hosts. > > > > > > > > Uusage example: > > > > > > > > meson --cross-file config/x86/cross-i686-linux-gcc build-i686 > > > > ninja -C build-i686 > > > > > > > > Signed-off-by: Lance Richardson > > > > --- > > > > Red Hat distros use a different name for the 32-bit pkg-config > > > > command from most other distros, maybe there is a better way > > > > to handle this than using separate files. > > > > > > > > Others will probably have better naming suggestions for the files. > > > > > > > Just to note that rather than using cross-files, building i686 on x86_64 > > > should be possible by just setting environment variables. > > > > > > For example, on Ubuntu 20.04, this works for me: > > > > > > PKG_CONFIG_LIBDIR=/usr/lib/i386-linux-gnu/pkgconfig CFLAGS='-m32' LDFLAGS='-m32' meson --werror build-32bit > > > ninja -C build-32bit/ > > > > > > For Fedora or Redhat system the PKG_CONFIG_LIBDIR will be different (I > > > think just /usr/lib/pkgconfig), but the rest should work identically. > > > > Thanks, that does work, although I'll have some trouble remembering it > > for future > > Would it help to have this command in devtools/test-meson-builds.sh ? > I think it would help, although using cross-files was suggested when that was proposed here: http://patchwork.dpdk.org/patch/69067/ Having the i686 build command in a document like the GSG might be helpful as well. Ideally it seems there should be a consistent way to build for different architectures using meson, I think we mostly have that now with the native architecture being used by default and otherwise using a cross-file found under config//. Thanks, Lance