From: Tomohiro Masubuchi <bucchi@e-ml.jp>
To: buildroot@busybox.net
Subject: [Buildroot] problem with openssh
Date: Fri, 08 Jun 2007 13:52:43 +0900 [thread overview]
Message-ID: <4668E09B.1000200@e-ml.jp> (raw)
In-Reply-To: <20070606235535.ddc532ee.philippe.ney@pardes.ws>
Hi all,
Elia Yehuda wrote:
> Ive been trying to compile openssh using buildroot, and just like
> samba, it compiles fine but any executable halts with "segmentation
> fault".
I found out that the cause of this problem originated in
__progname = NULL in uClibc-0.9.29.
The UCLIBC_HAS___PROGNAME is enabled in uClibc-0.9.29.config,
but UCLIBC_HAS_PROGRAM_INVOCATION_NAME is disabled.
Under this condition, it seems to become __progname = NULL. (uclibc's bug??)
In uClibc-0.9.28.config, both UCLIBC_HAS_PROGRAM_INVOCATION_NAME and
UCLIBC_HAS___PROGNAME is not exist. These become disabled.
In this case, symbol __progname was not exist. Then openssh will be
configured to not use __progname. Therefore this problem doesn't
happen in uClibc-0.9.28.
To solve this problem in uClibc-0.9.29, the following sentences of
toolchain/uClibc/uClibc-0.9.29.config are changed, and rebuild uclibc.
# UCLIBC_HAS_PROGRAM_INVOCATION_NAME is not set
to
UCLIBC_HAS_PROGRAM_INVOCATION_NAME=y
It works fine with arm(iwmmxt), gcc-4.2.0, binutils-2.17.50.0.16,
uClibc-0.9.29.
Tomohiro
next prev parent reply other threads:[~2007-06-08 4:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 14:00 [Buildroot] problem with openssh z4ziggy
2007-06-06 2:35 ` z4ziggy
2007-06-06 8:09 ` Philippe Ney
[not found] ` <e19d85410706060839l6baf072cte7a5c9c9d58b67ab@mail.gmail.com>
[not found] ` <e19d85410706061235g63cadda9s364849b0737a39ec@mail.gmail.com>
2007-06-06 21:55 ` Philippe Ney
2007-06-08 4:52 ` Tomohiro Masubuchi [this message]
2007-06-08 9:51 ` Konstantin Kletschke
2007-06-11 9:21 ` [Buildroot] problem with openssh/samba Tomohiro Masubuchi
2007-06-11 12:05 ` Konstantin Kletschke
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=4668E09B.1000200@e-ml.jp \
--to=bucchi@e-ml.jp \
--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 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.