All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming-Ching Tiew <mingching.tiew@redtone.com>
To: buildroot@busybox.net
Subject: [Buildroot] can't develope any programs using ssl in the root
Date: Fri, 25 Jan 2008 09:02:35 +0800	[thread overview]
Message-ID: <051301c85eed$f9167dc0$8119fea9@MingChing> (raw)
In-Reply-To: 20080124223846.GD3397@cloud.net.au


From: "Hamish Moffatt" <hamish@cloud.net.au>
> > >
> > > 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.
> 
> From your config.log snippet it appears that configure is using your
> native gcc (not the cross-compiler), which is using headers from
> /usr. That looks like a bug, either in the configure script or in the
> relevant .mk files for programs that use OpenSSL.
> 

No, not quite. The config.log is obtained from the chroot to the
rootfs, and the so-called native gcc, is the gcc compiled from the
cross compiler, there is no cross compilers involved.

Regards.

      reply	other threads:[~2008-01-25  1:02 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   ` [Buildroot] [Merak Spam 5.26] can't develope any programs using ssl in the root Hamish Moffatt
2008-01-25  1:02     ` Ming-Ching Tiew [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='051301c85eed$f9167dc0$8119fea9@MingChing' \
    --to=mingching.tiew@redtone.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 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.