* [Buildroot] can't develope any programs using ssl in the root
@ 2008-01-24 3:15 Ming-Ching Tiew
2008-01-24 1:44 ` [Buildroot] [Merak Spam 5.26] " Ming-Ching Tiew
0 siblings, 1 reply; 6+ messages in thread
From: Ming-Ching Tiew @ 2008-01-24 3:15 UTC (permalink / raw)
To: buildroot
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.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Buildroot] [Merak Spam 5.26] can't develope any programs using ssl in the root
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
2008-01-24 8:28 ` Thomas Lundquist
2008-01-24 22:38 ` [Buildroot] [Merak Spam 5.26] can't develope any programs using ssl in the root Hamish Moffatt
0 siblings, 2 replies; 6+ messages in thread
From: Ming-Ching Tiew @ 2008-01-24 1:44 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [Merak Spam 5.26] can't develope any programs using ssl in the root
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
1 sibling, 1 reply; 6+ messages in thread
From: Thomas Lundquist @ 2008-01-24 8:28 UTC (permalink / raw)
To: buildroot
On Thu, Jan 24, 2008 at 09:44:10AM +0800, Ming-Ching Tiew wrote:
>
> 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.
weird but not sure why.
> 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.
Not unless you want to build within the buildroot. I do sstrip on all
libraries on the resulting rootfs (floppyfw and others) but you are
probably right about sstripping when you have
CONFIG_BR2_PACKAGE_GCC_TARGET set.
When building the floppyfw devkit I also set CONFIG_BR2_STRIP_none.
I would consider it a but if any of the packages .mk files
does strip anything even when CONFIG_BR2_STRIP_none is set.
Bbut stripping the libraries when the target is a normal rootfs seems
correct to me.
Thomas.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] sstrip and segmentation violation ( was: can't develope any programs using ssl in the root )
2008-01-24 8:28 ` Thomas Lundquist
@ 2008-01-24 9:30 ` Ming-Ching Tiew
0 siblings, 0 replies; 6+ messages in thread
From: Ming-Ching Tiew @ 2008-01-24 9:30 UTC (permalink / raw)
To: buildroot
From: "Thomas Lundquist" <lists@zelow.no>
>
> > 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.
>
> Not unless you want to build within the buildroot. I do sstrip on all
> libraries on the resulting rootfs (floppyfw and others) but you are
> probably right about sstripping when you have
> CONFIG_BR2_PACKAGE_GCC_TARGET set.
>
> When building the floppyfw devkit I also set CONFIG_BR2_STRIP_none.
>
> I would consider it a but if any of the packages .mk files
> does strip anything even when CONFIG_BR2_STRIP_none is set.
>
> Bbut stripping the libraries when the target is a normal rootfs seems
> correct to me.
>
Oh I see. This buildroot thingie is rather new to me, so I am gaining
experience on it.
So it not quite a bug then, it is an not-so-obvious feature which
one can tumble on it. :-)
Last but not least, I seem to only get all the wrong things with me now.
I managed to compile the rootfs.i686.ext2, using a few different
combinations of gcc ( 3.4.6, 4.1.0, 4.2.0 ), uclibc version ( 0.9.28.3
and 0.9.29 ). But consistantly I get random segmentation violation
error when I compile stuff inside the rootfs. Looks like stack
corruption or something. Now perhaps I need to change my host
OS compiler instead ( I am using 4.1.2 20061028 ).
Anyone knows if the host compiler version will have an impact
on the quality of the rootfs ?
Regards.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [Merak Spam 5.26] can't develope any programs using ssl in the root
2008-01-24 1:44 ` [Buildroot] [Merak Spam 5.26] " Ming-Ching Tiew
2008-01-24 8:28 ` Thomas Lundquist
@ 2008-01-24 22:38 ` Hamish Moffatt
2008-01-25 1:02 ` [Buildroot] " Ming-Ching Tiew
1 sibling, 1 reply; 6+ messages in thread
From: Hamish Moffatt @ 2008-01-24 22:38 UTC (permalink / raw)
To: buildroot
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] can't develope any programs using ssl in the root
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
0 siblings, 0 replies; 6+ messages in thread
From: Ming-Ching Tiew @ 2008-01-25 1:02 UTC (permalink / raw)
To: buildroot
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2008-01-25 1:02 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 ` [Buildroot] " Ming-Ching Tiew
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox