This is a multi-part message in MIME format.

------_=_NextPart_001_01C6E413.7F3D06D6
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Attached is an email I sent to the openssl-users list about 2 weeks ago
on the same issue.

Glad to see I'm not the only one.

Tige=20


-----Original Message-----
From: owner-openssl-dev@openssl.org
[mailtowner-openssl-dev@openssl.org] On Behalf Of Martin Kraemer
Sent: Friday, September 29, 2006 12:53 PM
To: openssl-dev@openssl.org
Subject: [PATCH] openssl-0.9.7l "make install" fails in fips-1.0/
directory

Hello everyone,

I have a problem with openssl-0.9.7k and 0.9.7l; I am not using FIPS
(and the default also is to disable it).
On some platforms, I build the static libs only, and not the shared
libs.
At least on these platforms I had problems when doing "make install"
in the to-level directory, because it tries to install nonexistent
files:

--snip--
....
installing fips-1.0...
making install in fips/sha...
making install in fips/rand...
making install in fips/des...
making install in fips/aes...
making install in fips/dsa...
making install in fips/rsa...
making install in fips/dh...
making install in fips/hmac...
installing fipsld
cp: cannot stat `fipscanister.o': No such file or directory
cp: cannot stat `fipscanister.o.sha1': No such file or directory
*** Error code 1
make: Fatal error: Command failed for target `install'
Current working directory /home/martin/SRC/work/openssl-0.9.7l/fips-1.0
*** Error code 1
make: Fatal error: Command failed for target `install_sw'
(exit 1)
--snip--

The attached (ugly) patch fixes the problem by testing the install
target like it tests the build target (by checking for #define
OPENSSL_FIPS).

Am I the only user who observes this problem?

Martin
--=20
| Fujitsu Siemens
Fon: +49-89-636-46021, FAX: +49-89-636-48332 | 81730 Munich, Germany

------_=_NextPart_001_01C6E413.7F3D06D6
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit

X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: OpenSSL make instal error on Solaris 9
Date: Thu, 21 Sep 2006 17:12:34 -0400
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: OpenSSL make instal error on Solaris 9
Thread-Index: AcbdRvTmJBPdp13SS6+z2KnABSxD6AAZ9rXgAATyRDA=
From: "CHASTAIN, TIGE \(CONTRACTOR\)"
To:

I was having problems building OpenSSL 0.9.7k on Solaris 9. The error
was similar to problems other people have with building it on Solaris 9,
but not exactly the same.

The error is:

installing fips-1.0...
making install in fips/sha...
making install in fips/rand...
making install in fips/des...
making install in fips/aes...
making install in fips/dsa...
making install in fips/rsa...
making install in fips/dh...
making install in fips/hmac...
installing fipsld
cp: cannot access fipscanister.o
cp: cannot access fipscanister.o.sha1
*** Error code 2
make: Fatal error: Command failed for target `install'
Current working directory
/vol03/users/fin23292/openssl097k/openssl-0.9.7k/fips-1.0
*** Error code 1
make: Fatal error: Command failed for target `install_sw'

Strangly enough, during compile, no object files are created in the
fips-1.0 directlory. I've also noticed that even though I specified
no-fips to the Configure script, fips is still being processed.

Here are my build directives and my environmnet settings:

/Configure --prefix=3D/export/home/fin23292/openssl097k
--openssldir=3D/export/home/fin23292/openssl097k no-fips -fPIC
solaris-sparcv9-gcc

=09
PATH=3D/opt/sfw/gcc-3/bin:/usr/bin:/bin:/sbin:/usr/sbin:/usr/ccs/bin:/usr=
/
ucb:/usr/contrib/bin
LOGNAME=3Dfin23292
USER=3Dfin23292
SHELL=3D/bin/ksh
HOME=3D/export/home/fin23292
TERM=3Dxterm
PWD=3D/export/home/fin23292/openssl097k
TZ=3DUS/Eastern

Here is the version of Solaris 9, for reference:

$ cat /etc/release
Solaris 9 9/05 s9s_u8wos_05 SPARC
Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 04 August 2005

I pinned down the issue to be the "make" binary shipped with Solaris 9.
If I start fresh using GNU make, I do not get this error and everything
works fine. Using GCC or the Sun Workshop compiler make no difference.
I ran test builds against 0.9.8c, 0.9.7k, 0.9.7j, and 0.9.7i. Here are
my results:

0.9.8c/gcc/make success =20
0.9.8c/gcc/gmake success =20
0.9.8c/cc/make success =20
0.9.8c/cc/gmake success =20
=20
0.9.7k/gcc/make failed =20
0.9.7k/gcc/gmake success =20
0.9.7/cc/make failed =20
0.9.7k/cc/gmake success =20
=20
0.9.7j/gcc/make failed =20
0.9.7j/gcc/gmake success =20
0.9.7j/cc/make failed =20
0.9.7j/cc/gmake success =20

0.9.7i/gcc/make success
0.9.7i/gcc/gmake success
0.9.7i/cc/make success
0.9.7i/cc/gmake success

I thought someone might find this of interest.

Tige

------_=_NextPart_001_01C6E413.7F3D06D6--
__________________________________________________ ____________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majordomo@openssl.org