From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8916] New: LDFLAGS pass to openssh
Date: Tue, 10 May 2016 16:40:18 +0000 [thread overview]
Message-ID: <bug-8916-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8916
Bug ID: 8916
Summary: LDFLAGS pass to openssh
Product: buildroot
Version: unspecified
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: yxygyxyg at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
The fail message we obtain in buildroot-compiled chroot environment:
bash-4.3# ssh
bash: /usr/bin/ssh: No such file or directory
It happens because ssh execute file does not contain proper dynamic linker way:
# readelf /tmp/usr/bin/ssh -l
...
[Requesting program interpreter:
/home/cf/e2k/mcst.rel-21-0.fs/2016-04-12/e2k-generic-linux.cross/lib64/ld-linux.so.2]
...
The proper way to dynamic linker we set with
BR2_TARGET_LDFLAGS="-Wl,-dynamic-linker,/lib/ld-linux.so.2" option in .config
file. This scheme works fine in different packages (busybox, bash ...).
In case of openssh package the option does not pass through
package/openssh/openssh.mk file:
...
OPENSSH_CONF_ENV = LD="$(TARGET_CC)" LDFLAGS="$(TARGET_CFLAGS)"
...
Here internal openssh option LDFLAGS contain only common $(TARGET_CFLAGS).
Common $(TARGET_LDFLAGS) does not pass inside openssh build system here.
If we change this line to the next:
...
OPENSSH_CONF_ENV = LD="$(TARGET_CC)" LDFLAGS="$(TARGET_CFLAGS)
$(TARGET_LDFLAGS)"
...
ssh works fine.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-05-10 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 16:40 bugzilla at busybox.net [this message]
2016-09-12 15:44 ` [Buildroot] [Bug 8916] LDFLAGS pass to openssh bugzilla at busybox.net
2016-09-16 13:28 ` bugzilla at busybox.net
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-8916-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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