Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ming-Ching Tiew <mingching.tiew@redtone.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Merak Spam 5.26] can't develope any programs using ssl in the root
Date: Thu, 24 Jan 2008 09:44:10 +0800	[thread overview]
Message-ID: <00c401c85e2a$9de7f140$8119fea9@MingChing> (raw)
In-Reply-To: 479802C7.9090108@redtone.com


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.

BTW, the sstrip thingie looks to me also a bug. It happens to not
just SSL shared library. The uClibc libraries could also be
sstripped. This will be quite disasterous.

----- Original Message ----- 
From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: <buildroot@uclibc.org>
Sent: Thursday, January 24, 2008 11:15 AM
Subject: [Merak Spam 5.26] [Buildroot] can't develope any programs using ssl in the
root


>
> 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
> configure:12881: $? = 0
> configure:12885: test -z
>              || test ! -s conftest.err
> configure:12888: $? = 0
> configure:12891: test -s conftest
> configure:12894: $? = 0
> configure:12907: result: yes
> configure:12934: checking openssl/evp.h usability
> configure:12946: gcc -c -DINET6 -g -O2  -I./../libpcap-0.9.5
> -I/usr/include conftest.c >&5
> In file included from /usr/include/openssl/asn1.h:68,
>                  from /usr/include/openssl/rsa.h:63,
>                  from /usr/include/openssl/evp.h:150,
>                  from conftest.c:102:
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:301: error:
> expected specifier-qualifier-list before 'BIGNUM'
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:314: error:
> expected specifier-qualifier-list before 'BIGNUM'
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:331: error:
> expected declaration specifiers or '...' before 'BN_GENCB'
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:335: error:
> expected ')' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:393: error:
> expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:395: error:
> expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:397: error:
> expected ')' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:399: error:
> expected ')' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:400: error:
> expected ')' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:401: error:
> expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:402: error:
> expected ')' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:403: error:
> expected ')' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:404: error:
> expected ')' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:405: error:
> expected ')' before '*' token
> /usr/lib/gcc/i686-linux-uclibc/4.2.0/include/openssl/bn.h:406: error:
> expected ')' before '*' token
>
> Anyone has a clue ?
>
>
>
> --------------------------------------------
> 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

  reply	other threads:[~2008-01-24  1:44 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 ` Ming-Ching Tiew [this message]
2008-01-24  8:28   ` [Buildroot] [Merak Spam 5.26] " 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     ` [Buildroot] " 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='00c401c85e2a$9de7f140$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox