From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14256] New: Compiling with static libraries on s390x error
Date: Wed, 06 Oct 2021 11:07:13 +0000 [thread overview]
Message-ID: <bug-14256-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14256
Bug ID: 14256
Summary: Compiling with static libraries on s390x error
Product: buildroot
Version: 2021.08
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: raul.cabello@suse.com
CC: buildroot@uclibc.org
Target Milestone: ---
Hello,
When I try to compile using static libraries with s390x as a target I get the
following error:
The directory that should contain system headers does not exist:
/usr/src/buildroot/output/per-package/host-gcc-final/host/s390x-buildroot-linux-gnu/sysroot/usr/include
My .config file is attached. These are the steps I did to generate my .config
file:
- make menuconfig
- Select Target -> Target Architecture -> s390x
- Select Build Options -> Libraries -> static only
- exit and save .config
Then if I run make with this config I get error I mentioned above.
It works fine if I select shared libraries instead of static.
Operating System: openSUSE Leap 15.3
Kernel: Linux 5.3.18-57-default
Architecture: x86-64
Thank you.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-10-06 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 11:07 bugzilla [this message]
2021-10-06 11:13 ` [Buildroot] [Bug 14256] Compiling with static libraries on s390x error bugzilla
2021-10-06 20:25 ` bugzilla
2021-10-06 20:42 ` bugzilla
2021-10-07 7:37 ` bugzilla
2021-10-08 19:46 ` bugzilla
2024-06-15 14:59 ` bugzilla
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=bug-14256-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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