From: Oscar Gomez Fuente <oscargomezf@gmail.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] How to select python-cryptograhy package
Date: Mon, 23 May 2022 12:22:03 +0200 [thread overview]
Message-ID: <CALtfCQY1a6sjLNUh42zsrsu1hPLTMHNDj4+5v5k8w8kv8u6tmg@mail.gmail.com> (raw)
In-Reply-To: <87r14kq55b.fsf@tarshish>
Hi Baruch,
On Mon, 23 May 2022 at 05:50, Baruch Siach <baruch@tkos.co.il> wrote:
>
> So BR2_HOSTARCH should be "x86_64". Is that what you see when you lookup
> BR2_HOSTARCH in menuconfig?
YES
> What is the output of 'gcc -v' on your host?
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
9.4.0-1ubuntu1~20.04.1'
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2
--prefix=/usr --with-gcc-major-version-only --program-suffix=-9
--program-prefix=x86_64-linux-gnu- --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --libdir=/usr/lib
--enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-9-Av3uEd/gcc-9-9.4.0/debian/tmp-nvptx/usr,hsa
--without-cuda-driver --enable-checking=release
--build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-23 10:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 15:25 [Buildroot] How to select python-cryptograhy package Oscar Gomez Fuente
2022-05-21 20:22 ` Baruch Siach via buildroot
2022-05-22 18:45 ` Oscar Gomez Fuente
2022-05-23 3:38 ` Baruch Siach via buildroot
2022-05-23 10:22 ` Oscar Gomez Fuente [this message]
2022-05-23 15:38 ` Baruch Siach via buildroot
2022-05-23 16:07 ` Oscar Gomez Fuente
2022-05-24 19:14 ` Baruch Siach via buildroot
2022-05-25 5:31 ` Oscar Gomez Fuente
2022-05-25 6:05 ` Baruch Siach via buildroot
2022-05-25 6:28 ` James Hilliard
2022-05-25 7:01 ` Baruch Siach via buildroot
2022-05-25 7:36 ` James Hilliard
2022-06-02 17:00 ` Thomas Petazzoni via buildroot
2022-06-03 13:47 ` Baruch Siach via buildroot
2022-06-03 14:03 ` Thomas Petazzoni via buildroot
2022-05-24 20:24 ` Fabio Estevam
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=CALtfCQY1a6sjLNUh42zsrsu1hPLTMHNDj4+5v5k8w8kv8u6tmg@mail.gmail.com \
--to=oscargomezf@gmail.com \
--cc=baruch@tkos.co.il \
--cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.