Skip to contentSkip to conversation

Openssl won't compile

Buildroot Nathanael D. Noblet 2 participants 4 messages Jul 23, 2008 – Jul 24, 2008

lore
Share & tools
lore
#0 lore raw

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.

Signature · 3 lines
Nathanael d. Noblet
Gnat Solutions, Inc
T: 403.875.4613
#1 lore raw
Quoted 7 lines · Nathanael D. Noblet

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.

Hamish

Signature · 1 line
Hamish Moffatt VK3SB <[email protected]> <[email protected]>
#2 lore raw
Quoted 11 lines · Hamish Moffatt
Quoted 7 lines · Nathanael D. Noblet

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....

Signature · 3 lines
Nathanael d. Noblet
Gnat Solutions, Inc
T: 403.875.4613
#3 lore raw
Quoted 8 lines · Nathanael D. Noblet
Quoted 7 lines · Hamish Moffatt
Quoted 6 lines · Nathanael D. Noblet

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.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

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....

I'm using 4.1.2 because I couldn't get 4.2 to build for armeb with either OABI or EABI, though that was about 8-9 months ago. I'm using OABI with 4.1.2 successfully (I don't think EABI builds though).

What is your target hardware?

gcc-3.1 is old; you might be able to get away with 3.3 but 4.x would be much better (and you'll have more chance of getting assistance from the community).

Hamish

Signature · 1 line
Hamish Moffatt VK3SB <[email protected]> <[email protected]>