From: Joe <zentrale.at.work@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] strip problem
Date: Tue, 22 Jan 2008 09:15:23 +0100 [thread overview]
Message-ID: <4795A61B.7050500@gmail.com> (raw)
In-Reply-To: <033d01c85c9a$0d4713a0$8119fea9@MingChing>
Dear Mr. Ming-Ching Tiew,
for i have not the same problem as you, i am clearly not the intended
recipient of this message. To avoid being sued by you and/or your
lawyers, i hereby notify you that i have not read the message and do not
want to use it in any way. For the misdelivered message, you can fetch
it in my office today, from 13:00 til 15:00, for i am not allowed to
retain any possible copies. Please inform me if you need GPS coordinates.
Yours sincerely, Joe
Ming-Ching Tiew schrieb:
> I have been having this big problem with the buildroot,
> which I finally beginning to have some clues that it is likely
> due to the 'strip' problem.
>
> I select sstrip from the make menuconfig, under the presumption
> that it should only do it on the executables, and then
> I find that the 'strings libcrypto.0.9.7.so |grep MD5_Init'
> returns nothing.
>
> It seems to allow sstrip to happen on shared library.
>
> I don't know how many other places where such thing
> is happen to the whole make scripts.
>
> Wonder if anyone else has the same problem with me ?
>
>
>
> --------------------------------------------
> Important Warning!
>
> ***************************
>
> This electronic communication (including any attached files) may contain confidential and/or legally privileged information and is only intended for the use of the person to whom it is addressed. If you are not the intended recipient, you do not have permission to read, use, disseminate, distribute, copy or retain any part of this communication or its attachments in any form. If this e-mail was sent to you by mistake, please take the time to notify the sender so that they can identify the problem and avoid any more mistakes in sending e-mail to you. The unauthorised use of information contained in this communication or its attachments may result in legal action against any person who uses it.
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
--
Sepp "ZaP" Holzmayr
please reply to:
zentrale.at.work at gmail.com
watch out for:
www.rocksociety.de
prev parent reply other threads:[~2008-01-22 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 1:56 [Buildroot] strip problem Ming-Ching Tiew
2008-01-22 8:15 ` Joe [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=4795A61B.7050500@gmail.com \
--to=zentrale.at.work@gmail.com \
--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