From: Peter Seiderer <ps.report@gmx.net>
To: "John" <joblacker@cfl.rr.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] make failure trying to buildroot for raspberry pi 3 using external toolchain
Date: Fri, 22 Oct 2021 19:50:46 +0200 [thread overview]
Message-ID: <20211022195046.476ef082@gmx.net> (raw)
In-Reply-To: <000201d7c74e$f2d6aa10$d883fe30$@cfl.rr.com>
Hello John,
On Fri, 22 Oct 2021 10:13:12 -0400, "John" <joblacker@cfl.rr.com> wrote:
> I'm trying to perform a make using the latest buildroot version (2021.08.1)
> but it fails at the point of trying to build libgpg-error. I'm running on a
> Ubuntu 20.04 VM under
>
> Windows 10 VBox. Here's what I believe is the pertinent output info:
>
>
>
> configure: WARNING: unrecognized options: --disable-gtk-doc,
> --disable-gtk-doc-html, --disable-doc, --disable-docs,
> --disable-documentation, --with-xmlto, --with-fop, --enable-ipv6,
> --disable-nls
>
>
>
> GPGME v1.15.1 has been configured as follows:
>
>
>
> Revision: bb988077 (48024)
>
> Platform: arm-buildroot-linux-gnueabihf
>
>
>
> UI Server: yes
>
> FD Passing: yes
>
>
>
> Language bindings: cl cpp
>
>
>
> Mismatches between the target platform and the to
>
> be used libraries have been been detected for:
>
> libgpg-error
>
> Please check above for warning messages.
>
> End of output log:
>
>
>
> libtool: compile:
> /home/jb/GitHub/buildroot/output/host/bin/armv8-rpi3-linux-gnueabihf-gcc
> -DHAVE_CONFIG_H -I. -I../conf -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -D_FILE_OFFSET_BITS=64
> -I/home/jb/GitHub/buildroot/output/host/arm-buildroot-linux-gnueabihf/sysroo
> t/usr/bin/../../usr/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -D_FILE_OFFSET_BITS=64 -Os -g0 -D_FORTIFY_SOURCE=1 -Wall -Wcast-align
> -Wshadow -Wstrict-prototypes -Wno-format-y2k -Wno-missing-field-initializers
> -Wno-sign-compare -Wno-format-zero-length -Wno-format-truncation
> -Wno-sizeof-pointer-div -c debug.c -fPIC -DPIC -o .libs/debug.o
>
> libtool: compile:
> /home/jb/GitHub/buildroot/output/host/bin/armv8-rpi3-linux-gnueabihf-gcc
> -DHAVE_CONFIG_H -I. -I../conf -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -D_FILE_OFFSET_BITS=64
> -I/home/jb/GitHub/buildroot/output/host/arm-buildroot-linux-gnueabihf/sysroo
> t/usr/bin/../../usr/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -D_FILE_OFFSET_BITS=64 -Os -g0 -D_FORTIFY_SOURCE=1 -Wall -Wcast-align
> -Wshadow -Wstrict-prototypes -Wno-format-y2k -Wno-missing-field-initializers
> -Wno-sign-compare -Wno-format-zero-length -Wno-format-truncation
> -Wno-sizeof-pointer-div -c version.c -fPIC -DPIC -o .libs/version.o
>
> make[2]: *** [Makefile:534: all-recursive] Error 1
>
> make[1]: *** [package/pkg-generic.mk:270:
> /home/jb/GitHub/buildroot/output/build/libgpgme-1.15.1/.stamp_built] Error 2
>
> make: *** [Makefile:84: _all] Error 2
>
>
>
> Perhaps I have a configuration error but I don't know what it is.
Your log seems at least incomplete, the first part seems to be
from libgpg-error, the failing package is libgpgme...
Did you do a complete re-build after package selection changes
(see [1])?
In case the error persists after a complete re-build please provide
a minimal .config (or defconfig) file to reproduce the error...
Regards,
Peter
[1] https://buildroot.org/downloads/manual/manual.html#full-rebuild
>
> Please help.
>
>
>
> John Blacker
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-10-22 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 14:13 [Buildroot] make failure trying to buildroot for raspberry pi 3 using external toolchain John
2021-10-22 17:50 ` Peter Seiderer [this message]
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=20211022195046.476ef082@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=joblacker@cfl.rr.com \
/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