Re: problems compiling i386 from source (patching)

2014-12-13 Thread lists
On Fri, Dec 12, 2014 at 10:46:01AM +0100, Remco wrote:
 I ran into this as well, and found a similar problem on the net. 
 Unfortunately I didn't preserve the link but read on for a possible 
 solution.
 
 If your machine is upgraded all the time you may have /usr/bin/nawk getting 
 in the way, which should have been removed during the 5.5-5.6 upgrade. 
 (section 2. Files to delete and move) It seems I did at least the nsd part 
 of this section, so I just (re)ran the first set of rm-s, which includes 
 /usr/bin/nawk, and the problem was gone.

This is exactly what the cause was after some more investigation.



Re: problems compiling i386 from source (patching)

2014-12-12 Thread Remco
li...@ggp2.com wrote:

 I applied the newest unbound patch to several amd64 machines without
 trouble, and have had issues on several of my i386 boxes.  The initial
 error was probably the same as below, but led me to believe I may have
 had some kind of kernel or system frankenbox behavior.  I used cvs to
 pull all the latest sources (cvs -q up -rOPENBSD_5_6 -Pd is what I
 ran, so it should be the latest patch branch code),
 compiled/installed/rebooted to the new kernel, then ran through the
 steps for a make build.  make build bombed out on nsd with a similar
 error.
 
 in unbound, running make -f Makefile.bsd-wrapper obj works fine, but
 make -f Makefile.bsd-wrapper produces the error (which I believe is what
 I initially saw):
 
 ...
 checking for ctime_r... yes
 checking if make supports $ with implicit rule in scope... yes
 configure: Stripping extension flags...
 configure: creating ./config.status
 Bad system call (core dumped)
 config.status: creating Makefile
 Bad system call (core dumped)
 config.status: error: could not create Makefile
 *** Error 1 in /usr/src/usr.sbin/unbound (Makefile.bsd-wrapper:65
 '/usr/src/usr.sbin/unbound/obj/config.status')
 
 

I ran into this as well, and found a similar problem on the net. 
Unfortunately I didn't preserve the link but read on for a possible 
solution.

If your machine is upgraded all the time you may have /usr/bin/nawk getting 
in the way, which should have been removed during the 5.5-5.6 upgrade. 
(section 2. Files to delete and move) It seems I did at least the nsd part 
of this section, so I just (re)ran the first set of rm-s, which includes 
/usr/bin/nawk, and the problem was gone.



problems compiling i386 from source (patching)

2014-12-11 Thread lists
I applied the newest unbound patch to several amd64 machines without
trouble, and have had issues on several of my i386 boxes.  The initial
error was probably the same as below, but led me to believe I may have
had some kind of kernel or system frankenbox behavior.  I used cvs to
pull all the latest sources (cvs -q up -rOPENBSD_5_6 -Pd is what I
ran, so it should be the latest patch branch code),
compiled/installed/rebooted to the new kernel, then ran through the
steps for a make build.  make build bombed out on nsd with a similar
error.

in unbound, running make -f Makefile.bsd-wrapper obj works fine, but
make -f Makefile.bsd-wrapper produces the error (which I believe is what
I initially saw):

...
checking for ctime_r... yes
checking if make supports $ with implicit rule in scope... yes
configure: Stripping extension flags...
configure: creating ./config.status
Bad system call (core dumped) 
config.status: creating Makefile
Bad system call (core dumped) 
config.status: error: could not create Makefile
*** Error 1 in /usr/src/usr.sbin/unbound (Makefile.bsd-wrapper:65
'/usr/src/usr.sbin/unbound/obj/config.status')


Similarly, when troubleshooting nsd I get:

...
checking if libssl needs libdl... no
checking for openssl/ssl.h... yes
checking for openssl/err.h... yes
checking for openssl/rand.h... yes
configure: creating ./config.status
Bad system call (core dumped) 
config.status: creating Makefile
Bad system call (core dumped) 
config.status: error: could not create Makefile
*** Error 1 in /usr/src/usr.sbin/nsd (Makefile.bsd-wrapper:54
'config.status')


I have received these errors on both GENERIC and GENERIC.MP i386
machines so far.


Here's a dmesg from an MP machine:
OpenBSD 5.6-stable (GENERIC.MP) #0: Thu Dec 11 19:34:10 UTC 2014
root@:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Celeron(R) CPU E1200 @ 1.60GHz (GenuineIntel 686-class) 1.61 
GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF
real mem  = 524226560 (499MB)
avail mem = 503181312 (479MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 03/18/08, SMBIOS rev. 2.4 @ 0xe8170 (40 
entries)
bios0: vendor Intel Corp. version GLG3110H.86A.0004.2008.0318.2223 date 
03/18/2008
bios0: Intel Corporation DG31GL
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP APIC HPET MCFG
acpi0: wakeup devices P0P1(S3) PS2K(S3) PS2M(S3) UAR1(S3) P0P2(S4) USB0(S3) 
USB1(S3) USB2(S3) USB3(S3) EUSB(S3) MC97(S4) SLPB(S4) PWRB(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.0.0, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Celeron(R) CPU E1200 @ 1.60GHz (GenuineIntel 686-class) 1.60 
GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-64
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (P0P2)
acpicpu0 at acpi0:, C3, C2, C1, PSS
acpicpu1 at acpi0:, C3, C2, C1, PSS
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: PWRB
bios0: ROM list: 0xc/0xb400! 0xcb800/0x1800
cpu0: Enhanced SpeedStep 1600 MHz: speeds: 1600, 1200 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 Intel 82G33 Host rev 0x10
ppb0 at pci0 dev 1 function 0 Intel 82G33 PCIE rev 0x10: apic 0 int 16
pci1 at ppb0 bus 1
vga1 at pci0 dev 2 function 0 Intel 82G33 Video rev 0x10
intagp0 at vga1
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
No connectors reported connected with modes
Cannot find any crtc or sizes - going 1024x768
inteldrm0: 1024x768
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 0 int 23
uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 0 int 19
uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 0 int 18
uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 0 int 16
ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: apic 0 int 23
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
ppb1 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xe1
pci2 at ppb1 bus 2
fxp0 at pci2 dev 8 function 0 Intel PRO/100 VM rev 0x01, i82562: apic 0 int 
20, address 00:1c:c0:59:d7:29
inphy0 at fxp0 phy 1: i82562G 10/100 PHY, rev. 0

Re: problems compiling i386 from source (patching)

2014-12-11 Thread Theo de Raadt
 I applied the newest unbound patch to several amd64 machines without
 trouble, and have had issues on several of my i386 boxes.

You were running -stable:

OpenBSD 5.6-stable (GENERIC.MP) #0: Thu Dec 11 19:34:10 UTC 2014

 The initial
 error was probably the same as below, but led me to believe I may have
 had some kind of kernel or system frankenbox behavior.  I used cvs to
 pull all the latest sources (cvs -q up -rOPENBSD_5_6 -Pd is what I

Uhm, then you got brand new post-5.6 code, which is already highly
incompatible.

OpenBSD is a very fast-moving project.

You cannot do that.  We have changed some system calls already.



Re: problems compiling i386 from source (patching)

2014-12-11 Thread lists
On Thu, Dec 11, 2014 at 10:05:46PM -0700, Theo de Raadt wrote:
  I applied the newest unbound patch to several amd64 machines without
  trouble, and have had issues on several of my i386 boxes.
 
 You were running -stable:
 
 OpenBSD 5.6-stable (GENERIC.MP) #0: Thu Dec 11 19:34:10 UTC 2014
 
  The initial
  error was probably the same as below, but led me to believe I may have
  had some kind of kernel or system frankenbox behavior.  I used cvs to
  pull all the latest sources (cvs -q up -rOPENBSD_5_6 -Pd is what I
 
 Uhm, then you got brand new post-5.6 code, which is already highly
 incompatible.
 
 OpenBSD is a very fast-moving project.
 
 You cannot do that.  We have changed some system calls already.


Ah, I should have read more deeply into www.openbsd.org/stable.html .  I
was indeed confused how errata, -stable, and -current operated.  Sorry
for wasting everyone's time.

Thanks for helping me get this sorted.