From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] [Merak Spam 5.26] can't develope any programs using ssl in the root
Date: Fri, 25 Jan 2008 09:38:46 +1100 [thread overview]
Message-ID: <20080124223846.GD3397@cloud.net.au> (raw)
In-Reply-To: <00c401c85e2a$9de7f140$8119fea9@MingChing>
On Thu, Jan 24, 2008 at 09:44:10AM +0800, Ming-Ching Tiew wrote:
> > I wonder what I am doing wrong, I have enabled openssl and included
> > the header in the root, but in the root environment, I can't develope
> > any program which requires openssl, configure will fail with this error
> > ( the example below is tcpdump ) :-
> >
> > configure:12791: checking for SSLeay
> > configure:12833: result: /usr
> > configure:12845: checking for DES_cbc_encrypt in -lcrypto
> > configure:12875: gcc -o conftest -DINET6 -g -O2 -L/usr/lib conftest.c
> > -lcrypto ./../libpcap-0.9.5/libpcap.a >&5
[...]
>
> I have found a workaround for it, I delete the entire
>
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/
>
> Looks to me like a bug. Since I can proceed now, I am staying with
> this for a while.
next prev parent reply other threads:[~2008-01-24 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 3:15 [Buildroot] can't develope any programs using ssl in the root Ming-Ching Tiew
2008-01-24 1:44 ` [Buildroot] [Merak Spam 5.26] " Ming-Ching Tiew
2008-01-24 8:28 ` Thomas Lundquist
2008-01-24 9:30 ` [Buildroot] sstrip and segmentation violation ( was: can't develope any programs using ssl in the root ) Ming-Ching Tiew
2008-01-24 22:38 ` Hamish Moffatt [this message]
2008-01-25 1:02 ` [Buildroot] can't develope any programs using ssl in the root Ming-Ching Tiew
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=20080124223846.GD3397@cloud.net.au \
--to=hamish@cloud.net.au \
--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.