Re: pkg/34272: security/botan fails to install correctly

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR pkg/34272; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/34272: security/botan fails to install correctly 
Date: Fri, 25 Aug 2006 22:25:54 +0700

     Date:        Fri, 25 Aug 2006 11:40:16 +0000 (UTC)
     From:        Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
     Message-ID:  <20060825114016.32FEE63BB12%narn.NetBSD.org@localhost>
 
   |  Yes, it matters :-)
 
 OK, in that case ...   (from dmesg.boot)
 
 cpu0 at mainbus0: (uniprocessor)
 cpu0: Intel (686-class), 2998.70 MHz, id 0xf41
 cpu0: features bfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
 cpu0: features bfebfbff<PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX>
 cpu0: features bfebfbff<FXSR,SSE,SSE2,SS,HTT,TM,SBF>
 cpu0: features2 441d<SSE3,MONITOR,DS-CPL,CID,xTPR>
 cpu0: "Intel(R) Pentium(R) 4 CPU 3.00GHz"
 cpu0: I-cache 12K uOp cache 8-way
 cpu0: L2 cache 1 MB 64B/line 8-way
 cpu0: ITLB 4K/4M: 64 entries
 cpu0: DTLB 4K/4M: 64 entries
 cpu0: using thermal monitor 1
 cpu0: 32 page colors
 
   | What host name does it guess during the configure step?
 
 No idea?   How would I discover that, I don't see any immediate signs of any
 reference to host names at all.
 
 It does use -mcpu=i686 on the g++ compilations though.
 
   |  I'm considering either disabling it completely or making it an option
   |  similiar to mplayer et al.
 
 Please do.   What I'm doing is building binary packages.   I currently
 have no use for this one at all, but who knows, some time in the future.
 What does tend to happen to me however, is then when I want something like
 this, I need it installed in minutes, then often used for just a few minutes,
 then (often) removed again.   Pre-built binary packages are perfect for that.
 (I don't distribute the things, so licence terms of some packages that
 sometimes restrict against building packages are irrelevant).
 
 However, there's no guarantee that they'll be installed on the same system
 they're compiled on - embedding comilation discovered info into the binaries
 when making binary packages is a huge mistake.
 
 kre