Topic: Ubuntu build, 32 vs 64 bit bug

Question 1

WolfSSL 3-7 build fails on the 64 bit version of Ubuntu 1204 LTS and Ubuntu 1404 LTS

with the following error message: WARNING: 'aclocal-1.14' is missing on your system.

Interestingly, everything is OK with the 32 bit version of Ubuntu 1204 LTS and 1404 LTS.

with the same autoconf/automake versions as the 64 bit version

Any suggestion...

Question 2

Whats the preferred 64 bit linux OS for build/dev/run

Thanks

Share

Re: Ubuntu build, 32 vs 64 bit bug

Hi,

How and where did you download wolfSSL from?  Can you confirm what steps you are using to compile the library?  A normal build would be similar to:

unzip wolfssl-3.7.0.zip
cd wolfssl-3.7.0
./configure
make

Thanks,
Chris

Re: Ubuntu build, 32 vs 64 bit bug

Hello!

Sources were downloaded from your site a few days ago.

I've done the exact same build procedure both OS version.

Everything is OK for the 32 bit OS but fails on the 64 bit version.

Like you said, i've cd in wolfssl-3.7.0 directory then ./configure and make.

From my research on google, i can conclude that it is NOT a WolfSSL specific problem, but a Ubuntu 64 bit bug.

So i will keep looking for a working 64 bit OS, probably CentOS 7.

Anyway, thanks again for your time and your work.

Share

Re: Ubuntu build, 32 vs 64 bit bug

Hi,

I can confirm that wolfSSL 3.7.0 downloaded from the wolfssl.com download page compiles correctly on an Ubuntu 14.04 64-bit virtual machine.

I have the following aclocal version:

$ aclocal --version
aclocal (GNU automake) 1.14.1

What version of aclocal do you have installed?

Thanks,
Chris

Re: Ubuntu build, 32 vs 64 bit bug

Hello

I've reinstalled with the latest Ubuntu 14.04.3 and everything is compiling just fine.

I still get the same error with Ubuntu release 14.04.1 (iso: ubuntu-14.04.1-desktop-amd64.iso ),

but that's irrelevant now. Mea culpa; i should have updated to the latest Ubuntu.

Problem solved, thank you very very much for your time and patience.

Share

Re: Ubuntu build, 32 vs 64 bit bug

Hi,

Thanks for letting us know that upgrading to 14.04.3 fixed the issue.

Best Regards,
Chris