From: Nathanael D. Noblet <nathanael@gnat.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Openssl won't compile
Date: Wed, 23 Jul 2008 09:36:15 -0600 [thread overview]
Message-ID: <48874FEF.9070208@gnat.ca> (raw)
In-Reply-To: <20080723133519.GA27147@cloud.net.au>
Hamish Moffatt wrote:
> On Tue, Jul 22, 2008 at 09:13:56PM -0600, Nathanael D. Noblet wrote:
>> Hello,
>> Anyone experience difficulty compiling openssl (0.9.7m)? I get a
>> missing sys/timeb.h, upgrading to ssl 0.9.8g) is no better as the
>> patches don't apply and I'm not sure what the ones I couldn't fix were
>> doing.
>>
>> For what it is worth, I'm using gcc-3.1 and a daily snapshot of uclibc.
>
> I'm not having any trouble building it for armeb with gcc 4.1.2 with
> uClibc 0.9.29.
Using 0.9.29 I can't boot my target device. The rootfs boots in qemu but
I get a general protection fault on the real hardware. I've tried 4.2.x
and 4.3 and 4.4. Perhaps I'll try 4.1.2....
--
Nathanael d. Noblet
Gnat Solutions, Inc
T: 403.875.4613
next prev parent reply other threads:[~2008-07-23 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 3:13 [Buildroot] Openssl won't compile Nathanael D. Noblet
2008-07-23 13:35 ` Hamish Moffatt
2008-07-23 15:36 ` Nathanael D. Noblet [this message]
2008-07-24 0:58 ` Hamish Moffatt
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=48874FEF.9070208@gnat.ca \
--to=nathanael@gnat.ca \
--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.