Try using /usr/ucb/echo instead of just echo. This is what I found on Sun's web site:
==== The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be invoked if the user calls echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the black-slashed escape characters, and ksh's echo() also understands \a as the audible bell character; however, these commands do not have an -n option. ==== -- David Jacobson Martin Simmons <[EMAIL PROTECTED]> wrote: >>>>> On Tue, 7 Aug 2007 14:57:41 +0200 (CEST), Jan Pechanec via RT said: > > building the fips module ends with a tricky error: > > /usr/ccs/bin/ld: illegal option -- n > usage: ld [-6:abc:d:e:f:h:il:mo:p:rstu:z:B:CD:F:GI:L:M:N:P:Q:R:S:VY:?] > file(s) > [-64] enforce a 64-bit link-edit > ... > ... > > > the problem is that in general Solaris's echo's don't have '-n' so > this is a problem in fips-1.0/Makefile: > > fipscanister.o: fips_start.o $(LIBOBJ) $(FIPS_OBJ_LISTS) fips_end.o > @FIPS_BN_ASM=`for i in $(BN_ASM) ; do echo -n "../crypto/bn/$$i " ; > done`; \ > > not sure what is the best fix here, whether test for Solaris and set > it to "printf", or to replace it with printf right away, or something > different. After the fix the module builds fine. For more information about > echo's in Solaris, see: Have you tried just removing the -n? With luck the shell's word splitting will discard the newlines inside the backquotes. __Martin ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
