Re: openssl from pkgsrc

[Damian Lubosch <dl@xxxxxxxx>]

Am 09.08.2010 um 23:29 schrieb Sascha Wildner:

> On 8/9/2010 15:51, Damian Lubosch wrote:
>> Hello!
>> 
>> Is there any possibility to compile a current openssl into DragonflyBSD?
>> I have difficulty to compile the one from /usr/pkgsrc/security/openssl
>> 
>> The last lines where it stops compiling are:
>> cc -I. -I.. -I../include -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -pthread -D_THREAD_SAFE -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIOS -O3 -fomit-frame-pointer -Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -c  -o x86cpuid-elf.o x86cpuid-elf.s
>> x86cpuid-elf.s: Assembler messages:
>> x86cpuid-elf.s:13: Error: suffix or operands invalid for `push'
>> x86cpuid-elf.s:14: Error: suffix or operands invalid for `push'
>> [...]
> 
> Is it perhaps assuming you're on 32 bits? Do you have the configure output at hand?
> 
> Sascha

Hi!

Thanks for the hint! It really assumed that I would use 32-bit DragonFlyBSD. 

with DragonflyBSD:
===> Configuring for openssl-0.9.8o
cd /usr/pkgsrc/security/openssl/work/openssl-0.9.8o && /usr/pkg/bin/perl util/perlpath.pl /usr/pkg/bin/perl
Operating system: x86_64-whatever-dragonfly
Configuring for BSD-x86-elf
Configuring for BSD-x86-elf
. ..

With NetBSD 64 it writes:
===> Configuring for openssl-0.9.8o
cd /var/build/security/openssl/work/openssl-0.9.8o && /usr/pkg/bin/perl util/perlpath.pl /usr/pkg/bin/perl
Operating system: x86_64-whatever-netbsd
Configuring for NetBSD-x86_64
Configuring for NetBSD-x86_64
. ..

I changed /usr/pkgsrc/security/openssl/patches/patch-aa (with bmake make-patchsum) like this:

line 56
amd64-*-*bsd*)       OUT="BSD-x86_64" ;;

to
amd64-*-*bsd*|*-dragonfly*)  OUT="BSD-x86_64" ;;

Obviously, pkgsrc did not know that there is now a 64bit version of DragonFlyBSD.

It compiles now flawlessly, but how do I contact the openssl package maintainer to exchange the patch? pkgsrc.se lists only pkgsrc-users as maintainer. What is the correct protocol? Google didn't help so much...

Thanks,
Damian