From: Ming-Ching Tiew <mingching.tiew@redtone.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can't compile anything with using ssl in target system
Date: Sun, 27 Jan 2008 09:32:11 -0500 [thread overview]
Message-ID: <479C95EB.1030001@redtone.com> (raw)
Hmmm I also have tracked down the openssl problem.
The story is long. I have a copy of openssl 0.9.8 and the header
on my host. When running buildroot and producing a target gcc,
the gcc make script has a script called 'fixinc.sh' which scans
the include files for non-ansi compatible headers and fixes it
and make a fixed copy into it's down library directory,
/usr/lib/gcc/.../../include.
And openssl library happens to have one include file, namely
openssl/bn.h which is considered non-ansi compatible and
it shall be fixed !
Now because my host is using openssl 0.9.8 and the header
is different from 0.9.7 used by buildroot, this operation will
result in the target system has two version of bn.h, one
version 0.9.7 bn.h in /usr/include/openssl (original ) and
another version 0.9.8 bn.h in /us/lib/gcc/.../.../include/openssl
( and ansi-fixed ).
And because the one in usr/lib/gcc takes precedence and
hence resulting in compilation error.
What remains unanswered is why would gcc make script
'fixinc.sh' fixes the host's include files and include it in
the target system.
Cheers.
--------------------------------------------
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.
reply other threads:[~2008-01-27 14:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=479C95EB.1030001@redtone.com \
--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