amd64 cc error unknown argument '-msave-args'

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

amd64 cc error unknown argument '-msave-args'

John Rigg
I'm trying to compile a GENERIC.MP kernel on amd64
6.4 -stable. I've followed the instructions in the
FAQ for building a custom kernel, but the 'make'
step fails with an unknown argument: '-msave-args'
error. I've copied the compiler messages and dmesg
below. Suggestions for a cure or workaround would
be appreciated.=20

John


cat /usr/src/sys/arch/amd64/amd64/genassym.cf /usr/src/sys/arch/amd64/amd64=
/genassym.cf |  sh /usr/src/sys/kern/genassym.sh cc -no-integrated-as -g -W=
error -Wall -Wimplicit-function-declaration  -Wno-uninitialized -Wno-pointe=
r-sign  -Wframe-larger-than=3D2047 -Wno-address-of-packed-member -Wno-const=
ant-conversion -mcmodel=3Dkernel -mno-red-zone -mno-sse2 -mno-sse -mno-3dno=
w  -mno-mmx -msoft-float -fno-omit-frame-pointer -ffreestanding -fno-pie -m=
save-args -O2 -pipe -nostdinc -I/usr/src/sys -I/sys/arch/amd64/compile/GENE=
RIC.MP/obj -I/usr/src/sys/arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DK=
MEMSTATS -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM -DUVM=
_SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA -DEXT2FS=
 -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO -DFUSE -DSOC=
KET_SPLICE -DTCP_ECN -DTCP_SIGNATURE -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DE=
FLATE -DPIPEX -DMROUTING -DMPLS -DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DM=
TRR -DNTFS -DHIBERNATE -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DW=
SDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS=3D"6" -DX86EMU -DONEWIREV=
ERBOSE -DMULTIPROCESSOR -DMAXUSERS=3D80 -D_KERNEL -MD -MP -MF assym.P > ass=
ym.h.tmp
cc: error: unknown argument: '-msave-args'
*** Error 1 in /sys/arch/amd64/compile/GENERIC.MP (Makefile:1010 'assym.h')


dmesg
_____

OpenBSD 6.4 (GENERIC.MP) #6: Sat Jan 26 20:37:44 CET 2019
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENE=
RIC.MP
real mem =3D 4007526400 (3821MB)
avail mem =3D 3876790272 (3697MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (57 entries)
bios0: vendor Award Software International, Inc. version "F5" date 06/18/20=
08
bios0: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP SSDT HPET MCFG APIC
acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3)=
 USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PC=
E7(S4) PCE9(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimcfg0 at acpi0
acpimcfg0: addr 0xe0000000, bus 0-255
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Athlon(tm) Dual Core Processor 4850e, 2505.72 MHz, 0f-6b-02
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
ine 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 200MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Athlon(tm) Dual Core Processor 4850e, 2505.33 MHz, 0f-6b-02
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
ine 16-way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 21, 24 pins, remapped
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 3 (P2P_)
acpiprt2 at acpi0: bus -1 (PCE2)
acpiprt3 at acpi0: bus -1 (PCE3)
acpiprt4 at acpi0: bus -1 (PCE4)
acpiprt5 at acpi0: bus -1 (PCE5)
acpiprt6 at acpi0: bus -1 (PCE6)
acpiprt7 at acpi0: bus -1 (PCE7)
acpiprt8 at acpi0: bus -1 (PCE9)
acpiprt9 at acpi0: bus 2 (PCEA)
acpiprt10 at acpi0: bus -1 (PCEB)
acpiprt11 at acpi0: bus -1 (PCEC)
acpiprt12 at acpi0: bus 1 (AGP_)
acpicpu0 at acpi0: C1(@1 halt!), PSS
acpicpu1 at acpi0: C1(@1 halt!), PSS
acpibtn0 at acpi0: PWRB
acpicmos0 at acpi0
"PNP0C14" at acpi0 not configured
cpu0: PowerNow! K8 2505 MHz: speeds: 2500 2400 2200 2000 1800 1000 MHz
pci0 at mainbus0 bus 0
0:0:0: mem address conflict 0xe0000000/0x20000000
pchb0 at pci0 dev 0 function 0 "AMD RS780 Host" rev 0x00
ppb0 at pci0 dev 1 function 0 "AMD RS780 PCIE" rev 0x00
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 5 function 0 "ATI Radeon HD 3200" rev 0x00
drm0 at radeondrm0
radeondrm0: apic 2 int 18
azalia0 at pci1 dev 5 function 1 "ATI RS780 HD Audio" rev 0x00: msi
azalia0: no supported codecs
ppb1 at pci0 dev 10 function 0 "AMD RS780 PCIE" rev 0x00: msi
pci2 at ppb1 bus 2
re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x02: RTL8168C/8111C (0x3c0=
0), msi, address 00:1f:d0:86:00:60
rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 2
ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x00: apic 2 int 22, A=
HCI 1.1
ahci0: port 0: 3.0Gb/s
ahci0: port 2: 3.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: <ATA, Hitachi HDP72503, GM3O> SCSI3 0/direct =
fixed naa.5000cca34ddd54e3
sd0: 305244MB, 512 bytes/sector, 625140335 sectors
sd1 at scsibus1 targ 2 lun 0: <ATA, Hitachi HDP72503, GM3O> SCSI3 0/direct =
fixed naa.5000cca34ddd0950
sd1: 305244MB, 512 bytes/sector, 625140335 sectors
ohci0 at pci0 dev 18 function 0 "ATI SB700 USB" rev 0x00: apic 2 int 16, ve=
rsion 1.0, legacy support
ohci1 at pci0 dev 18 function 1 "ATI SB700 USB" rev 0x00: apic 2 int 16, ve=
rsion 1.0, legacy support
ehci0 at pci0 dev 18 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 17
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "ATI EHCI root hub" rev 2.00/1.00=
 addr 1
ohci2 at pci0 dev 19 function 0 "ATI SB700 USB" rev 0x00: apic 2 int 18, ve=
rsion 1.0, legacy support
ohci2: SMM does not respond, will reset
ohci3 at pci0 dev 19 function 1 "ATI SB700 USB" rev 0x00: apic 2 int 18, ve=
rsion 1.0, legacy support
ehci1 at pci0 dev 19 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 19
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "ATI EHCI root hub" rev 2.00/1.00=
 addr 1
piixpm0 at pci0 dev 20 function 0 "ATI SBx00 SMBus" rev 0x3a: SMI
iic0 at piixpm0
spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-6400CL5
spdmem1 at iic0 addr 0x51: 1GB DDR2 SDRAM non-parity PC2-6400CL5
spdmem2 at iic0 addr 0x52: 1GB DDR2 SDRAM non-parity PC2-6400CL6
spdmem3 at iic0 addr 0x53: 1GB DDR2 SDRAM non-parity PC2-6400CL6
pciide0 at pci0 dev 20 function 1 "ATI SB700 IDE" rev 0x00: DMA, channel 0 =
configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 1 drive 0
scsibus2 at atapiscsi0: 2 targets
cd0 at scsibus2 targ 0 lun 0: <ATAPI, iHAS124 C, LL0E> ATAPI 5/cdrom remova=
ble
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5
pcib0 at pci0 dev 20 function 3 "ATI SB700 ISA" rev 0x00
ppb2 at pci0 dev 20 function 4 "ATI SB600 PCI" rev 0x00
pci3 at ppb2 bus 3
envy0 at pci3 dev 7 function 0 "IC Ensemble Envy24 I/O Ctrlr" rev 0x02: api=
c 2 int 21
envy0: M-Audio Audiophile 2496, 2 inputs, 2 outputs
audio0 at envy0
midi0 at envy0: <Envy24 MIDI UART>
"TI TSB43AB23 FireWire" rev 0x00 at pci3 dev 14 function 0 not configured
ohci4 at pci0 dev 20 function 5 "ATI SB700 USB" rev 0x00: apic 2 int 18, ve=
rsion 1.0, legacy support
pchb1 at pci0 dev 24 function 0 "AMD AMD64 0Fh HyperTransport" rev 0x00
pchb2 at pci0 dev 24 function 1 "AMD AMD64 0Fh Address Map" rev 0x00
pchb3 at pci0 dev 24 function 2 "AMD AMD64 0Fh DRAM Cfg" rev 0x00
kate0 at pci0 dev 24 function 3 "AMD AMD64 0Fh Misc Cfg" rev 0x00: core rev=
 BH-G2
usb2 at ohci0: USB revision 1.0
uhub2 at usb2 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
 addr 1
usb3 at ohci1: USB revision 1.0
uhub3 at usb3 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
 addr 1
usb4 at ohci2: USB revision 1.0
uhub4 at usb4 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
 addr 1
usb5 at ohci3: USB revision 1.0
uhub5 at usb5 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
 addr 1
isa0 at pcib0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
it0 at isa0 port 0x2e/2: IT8718F rev 5, EC port 0x228
usb6 at ohci4: USB revision 1.0
uhub6 at usb6 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
 addr 1
vmm0 at mainbus0: SVM
ugen0 at uhub3 port 1 "Ultima USB Scanner" rev 1.10/1.00 addr 2
vscsi0 at root
scsibus3 at vscsi0: 256 targets
softraid0 at root
scsibus4 at softraid0: 256 targets
root on sd0a (d62a14d69a338a1c.a) swap on sd0b dump on sd0b
initializing kernel modesetting (RS780 0x1002:0x9610 0x1458:0xD000).
radeondrm0: 1440x900, 32bpp
wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0
wsdisplay0: screen 1-5 added (std, vt100 emulation)
ulpt0 at uhub0 port 3 configuration 1 interface 0 "Brother HL-5250DN" rev 2=
=2E00/1.00 addr 2
ulpt0: using bi-directional mode

Reply | Threaded
Open this post in threaded view
|

Re: amd64 cc error unknown argument '-msave-args'

Theo de Raadt-2
John Rigg <[hidden email]> wrote:

> I'm trying to compile a GENERIC.MP kernel on amd64
> 6.4 -stable.

No way, you are not.  Only -current has that, as of a few days ago.

 I've followed the instructions in the

> FAQ for building a custom kernel, but the 'make'
> step fails with an unknown argument: '-msave-args'
> error. I've copied the compiler messages and dmesg
> below. Suggestions for a cure or workaround would
> be appreciated.=20
>
> John
>
>
> cat /usr/src/sys/arch/amd64/amd64/genassym.cf /usr/src/sys/arch/amd64/amd64=
> /genassym.cf |  sh /usr/src/sys/kern/genassym.sh cc -no-integrated-as -g -W=
> error -Wall -Wimplicit-function-declaration  -Wno-uninitialized -Wno-pointe=
> r-sign  -Wframe-larger-than=3D2047 -Wno-address-of-packed-member -Wno-const=
> ant-conversion -mcmodel=3Dkernel -mno-red-zone -mno-sse2 -mno-sse -mno-3dno=
> w  -mno-mmx -msoft-float -fno-omit-frame-pointer -ffreestanding -fno-pie -m=
> save-args -O2 -pipe -nostdinc -I/usr/src/sys -I/sys/arch/amd64/compile/GENE=
> RIC.MP/obj -I/usr/src/sys/arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DK=
> MEMSTATS -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM -DUVM=
> _SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA -DEXT2FS=
>  -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO -DFUSE -DSOC=
> KET_SPLICE -DTCP_ECN -DTCP_SIGNATURE -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DE=
> FLATE -DPIPEX -DMROUTING -DMPLS -DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DM=
> TRR -DNTFS -DHIBERNATE -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DW=
> SDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS=3D"6" -DX86EMU -DONEWIREV=
> ERBOSE -DMULTIPROCESSOR -DMAXUSERS=3D80 -D_KERNEL -MD -MP -MF assym.P > ass=
> ym.h.tmp
> cc: error: unknown argument: '-msave-args'
> *** Error 1 in /sys/arch/amd64/compile/GENERIC.MP (Makefile:1010 'assym.h')
>
>
> dmesg
> _____
>
> OpenBSD 6.4 (GENERIC.MP) #6: Sat Jan 26 20:37:44 CET 2019
>     [hidden email]:/usr/src/sys/arch/amd64/compile/GENE=
> RIC.MP
> real mem =3D 4007526400 (3821MB)
> avail mem =3D 3876790272 (3697MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (57 entries)
> bios0: vendor Award Software International, Inc. version "F5" date 06/18/20=
> 08
> bios0: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H
> acpi0 at bios0: rev 0
> acpi0: sleep states S0 S1 S4 S5
> acpi0: tables DSDT FACP SSDT HPET MCFG APIC
> acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3)=
>  USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PC=
> E7(S4) PCE9(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 32 bits
> acpihpet0 at acpi0: 14318180 Hz
> acpimcfg0 at acpi0
> acpimcfg0: addr 0xe0000000, bus 0-255
> acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: AMD Athlon(tm) Dual Core Processor 4850e, 2505.72 MHz, 0f-6b-02
> cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
> 36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
> ,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
> cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
> ine 16-way L2 cache
> cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
> cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 200MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: AMD Athlon(tm) Dual Core Processor 4850e, 2505.33 MHz, 0f-6b-02
> cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
> 36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
> ,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
> cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
> ine 16-way L2 cache
> cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
> cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
> ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 21, 24 pins, remapped
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 3 (P2P_)
> acpiprt2 at acpi0: bus -1 (PCE2)
> acpiprt3 at acpi0: bus -1 (PCE3)
> acpiprt4 at acpi0: bus -1 (PCE4)
> acpiprt5 at acpi0: bus -1 (PCE5)
> acpiprt6 at acpi0: bus -1 (PCE6)
> acpiprt7 at acpi0: bus -1 (PCE7)
> acpiprt8 at acpi0: bus -1 (PCE9)
> acpiprt9 at acpi0: bus 2 (PCEA)
> acpiprt10 at acpi0: bus -1 (PCEB)
> acpiprt11 at acpi0: bus -1 (PCEC)
> acpiprt12 at acpi0: bus 1 (AGP_)
> acpicpu0 at acpi0: C1(@1 halt!), PSS
> acpicpu1 at acpi0: C1(@1 halt!), PSS
> acpibtn0 at acpi0: PWRB
> acpicmos0 at acpi0
> "PNP0C14" at acpi0 not configured
> cpu0: PowerNow! K8 2505 MHz: speeds: 2500 2400 2200 2000 1800 1000 MHz
> pci0 at mainbus0 bus 0
> 0:0:0: mem address conflict 0xe0000000/0x20000000
> pchb0 at pci0 dev 0 function 0 "AMD RS780 Host" rev 0x00
> ppb0 at pci0 dev 1 function 0 "AMD RS780 PCIE" rev 0x00
> pci1 at ppb0 bus 1
> radeondrm0 at pci1 dev 5 function 0 "ATI Radeon HD 3200" rev 0x00
> drm0 at radeondrm0
> radeondrm0: apic 2 int 18
> azalia0 at pci1 dev 5 function 1 "ATI RS780 HD Audio" rev 0x00: msi
> azalia0: no supported codecs
> ppb1 at pci0 dev 10 function 0 "AMD RS780 PCIE" rev 0x00: msi
> pci2 at ppb1 bus 2
> re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x02: RTL8168C/8111C (0x3c0=
> 0), msi, address 00:1f:d0:86:00:60
> rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 2
> ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x00: apic 2 int 22, A=
> HCI 1.1
> ahci0: port 0: 3.0Gb/s
> ahci0: port 2: 3.0Gb/s
> scsibus1 at ahci0: 32 targets
> sd0 at scsibus1 targ 0 lun 0: <ATA, Hitachi HDP72503, GM3O> SCSI3 0/direct =
> fixed naa.5000cca34ddd54e3
> sd0: 305244MB, 512 bytes/sector, 625140335 sectors
> sd1 at scsibus1 targ 2 lun 0: <ATA, Hitachi HDP72503, GM3O> SCSI3 0/direct =
> fixed naa.5000cca34ddd0950
> sd1: 305244MB, 512 bytes/sector, 625140335 sectors
> ohci0 at pci0 dev 18 function 0 "ATI SB700 USB" rev 0x00: apic 2 int 16, ve=
> rsion 1.0, legacy support
> ohci1 at pci0 dev 18 function 1 "ATI SB700 USB" rev 0x00: apic 2 int 16, ve=
> rsion 1.0, legacy support
> ehci0 at pci0 dev 18 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 17
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "ATI EHCI root hub" rev 2.00/1.00=
>  addr 1
> ohci2 at pci0 dev 19 function 0 "ATI SB700 USB" rev 0x00: apic 2 int 18, ve=
> rsion 1.0, legacy support
> ohci2: SMM does not respond, will reset
> ohci3 at pci0 dev 19 function 1 "ATI SB700 USB" rev 0x00: apic 2 int 18, ve=
> rsion 1.0, legacy support
> ehci1 at pci0 dev 19 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 19
> usb1 at ehci1: USB revision 2.0
> uhub1 at usb1 configuration 1 interface 0 "ATI EHCI root hub" rev 2.00/1.00=
>  addr 1
> piixpm0 at pci0 dev 20 function 0 "ATI SBx00 SMBus" rev 0x3a: SMI
> iic0 at piixpm0
> spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-6400CL5
> spdmem1 at iic0 addr 0x51: 1GB DDR2 SDRAM non-parity PC2-6400CL5
> spdmem2 at iic0 addr 0x52: 1GB DDR2 SDRAM non-parity PC2-6400CL6
> spdmem3 at iic0 addr 0x53: 1GB DDR2 SDRAM non-parity PC2-6400CL6
> pciide0 at pci0 dev 20 function 1 "ATI SB700 IDE" rev 0x00: DMA, channel 0 =
> configured to compatibility, channel 1 configured to compatibility
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus2 at atapiscsi0: 2 targets
> cd0 at scsibus2 targ 0 lun 0: <ATAPI, iHAS124 C, LL0E> ATAPI 5/cdrom remova=
> ble
> cd0(pciide0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5
> pcib0 at pci0 dev 20 function 3 "ATI SB700 ISA" rev 0x00
> ppb2 at pci0 dev 20 function 4 "ATI SB600 PCI" rev 0x00
> pci3 at ppb2 bus 3
> envy0 at pci3 dev 7 function 0 "IC Ensemble Envy24 I/O Ctrlr" rev 0x02: api=
> c 2 int 21
> envy0: M-Audio Audiophile 2496, 2 inputs, 2 outputs
> audio0 at envy0
> midi0 at envy0: <Envy24 MIDI UART>
> "TI TSB43AB23 FireWire" rev 0x00 at pci3 dev 14 function 0 not configured
> ohci4 at pci0 dev 20 function 5 "ATI SB700 USB" rev 0x00: apic 2 int 18, ve=
> rsion 1.0, legacy support
> pchb1 at pci0 dev 24 function 0 "AMD AMD64 0Fh HyperTransport" rev 0x00
> pchb2 at pci0 dev 24 function 1 "AMD AMD64 0Fh Address Map" rev 0x00
> pchb3 at pci0 dev 24 function 2 "AMD AMD64 0Fh DRAM Cfg" rev 0x00
> kate0 at pci0 dev 24 function 3 "AMD AMD64 0Fh Misc Cfg" rev 0x00: core rev=
>  BH-G2
> usb2 at ohci0: USB revision 1.0
> uhub2 at usb2 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
>  addr 1
> usb3 at ohci1: USB revision 1.0
> uhub3 at usb3 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
>  addr 1
> usb4 at ohci2: USB revision 1.0
> uhub4 at usb4 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
>  addr 1
> usb5 at ohci3: USB revision 1.0
> uhub5 at usb5 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
>  addr 1
> isa0 at pcib0
> isadma0 at isa0
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard
> pms0 at pckbc0 (aux slot)
> wsmouse0 at pms0 mux 0
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> it0 at isa0 port 0x2e/2: IT8718F rev 5, EC port 0x228
> usb6 at ohci4: USB revision 1.0
> uhub6 at usb6 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
>  addr 1
> vmm0 at mainbus0: SVM
> ugen0 at uhub3 port 1 "Ultima USB Scanner" rev 1.10/1.00 addr 2
> vscsi0 at root
> scsibus3 at vscsi0: 256 targets
> softraid0 at root
> scsibus4 at softraid0: 256 targets
> root on sd0a (d62a14d69a338a1c.a) swap on sd0b dump on sd0b
> initializing kernel modesetting (RS780 0x1002:0x9610 0x1458:0xD000).
> radeondrm0: 1440x900, 32bpp
> wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0
> wsdisplay0: screen 1-5 added (std, vt100 emulation)
> ulpt0 at uhub0 port 3 configuration 1 interface 0 "Brother HL-5250DN" rev 2=
> =2E00/1.00 addr 2
> ulpt0: using bi-directional mode
>

Reply | Threaded
Open this post in threaded view
|

Re: amd64 cc error unknown argument '-msave-args'

Theo de Raadt-2
And since you are doing this with -current *ALL OVER THE PLACE*
there are instructions that if you have trouble you should upgrade
to a snapshot.

Those instructions to exist the noise on the list everytime we
make a change and people don't notice or understand it and suddenly
they are in over their heads

*even our own developers* have to do that, from time to time



> John Rigg <[hidden email]> wrote:
>
> > I'm trying to compile a GENERIC.MP kernel on amd64
> > 6.4 -stable.
>
> No way, you are not.  Only -current has that, as of a few days ago.
>
>  I've followed the instructions in the
> > FAQ for building a custom kernel, but the 'make'
> > step fails with an unknown argument: '-msave-args'
> > error. I've copied the compiler messages and dmesg
> > below. Suggestions for a cure or workaround would
> > be appreciated.=20
> >
> > John
> >
> >
> > cat /usr/src/sys/arch/amd64/amd64/genassym.cf /usr/src/sys/arch/amd64/amd64=
> > /genassym.cf |  sh /usr/src/sys/kern/genassym.sh cc -no-integrated-as -g -W=
> > error -Wall -Wimplicit-function-declaration  -Wno-uninitialized -Wno-pointe=
> > r-sign  -Wframe-larger-than=3D2047 -Wno-address-of-packed-member -Wno-const=
> > ant-conversion -mcmodel=3Dkernel -mno-red-zone -mno-sse2 -mno-sse -mno-3dno=
> > w  -mno-mmx -msoft-float -fno-omit-frame-pointer -ffreestanding -fno-pie -m=
> > save-args -O2 -pipe -nostdinc -I/usr/src/sys -I/sys/arch/amd64/compile/GENE=
> > RIC.MP/obj -I/usr/src/sys/arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DK=
> > MEMSTATS -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM -DUVM=
> > _SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA -DEXT2FS=
> >  -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS -DFIFO -DFUSE -DSOC=
> > KET_SPLICE -DTCP_ECN -DTCP_SIGNATURE -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DE=
> > FLATE -DPIPEX -DMROUTING -DMPLS -DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DM=
> > TRR -DNTFS -DHIBERNATE -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DW=
> > SDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS=3D"6" -DX86EMU -DONEWIREV=
> > ERBOSE -DMULTIPROCESSOR -DMAXUSERS=3D80 -D_KERNEL -MD -MP -MF assym.P > ass=
> > ym.h.tmp
> > cc: error: unknown argument: '-msave-args'
> > *** Error 1 in /sys/arch/amd64/compile/GENERIC.MP (Makefile:1010 'assym.h')
> >
> >
> > dmesg
> > _____
> >
> > OpenBSD 6.4 (GENERIC.MP) #6: Sat Jan 26 20:37:44 CET 2019
> >     [hidden email]:/usr/src/sys/arch/amd64/compile/GENE=
> > RIC.MP
> > real mem =3D 4007526400 (3821MB)
> > avail mem =3D 3876790272 (3697MB)
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (57 entries)
> > bios0: vendor Award Software International, Inc. version "F5" date 06/18/20=
> > 08
> > bios0: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H
> > acpi0 at bios0: rev 0
> > acpi0: sleep states S0 S1 S4 S5
> > acpi0: tables DSDT FACP SSDT HPET MCFG APIC
> > acpi0: wakeup devices USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3)=
> >  USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PC=
> > E7(S4) PCE9(S4) [...]
> > acpitimer0 at acpi0: 3579545 Hz, 32 bits
> > acpihpet0 at acpi0: 14318180 Hz
> > acpimcfg0 at acpi0
> > acpimcfg0: addr 0xe0000000, bus 0-255
> > acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: AMD Athlon(tm) Dual Core Processor 4850e, 2505.72 MHz, 0f-6b-02
> > cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
> > 36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
> > ,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
> > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
> > ine 16-way L2 cache
> > cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
> > cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
> > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> > cpu0: apic clock running at 200MHz
> > cpu1 at mainbus0: apid 1 (application processor)
> > cpu1: AMD Athlon(tm) Dual Core Processor 4850e, 2505.33 MHz, 0f-6b-02
> > cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
> > 36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,RDTSCP,LONG,3DNOW2=
> > ,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP
> > cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/l=
> > ine 16-way L2 cache
> > cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
> > cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
> > ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 21, 24 pins, remapped
> > acpiprt0 at acpi0: bus 0 (PCI0)
> > acpiprt1 at acpi0: bus 3 (P2P_)
> > acpiprt2 at acpi0: bus -1 (PCE2)
> > acpiprt3 at acpi0: bus -1 (PCE3)
> > acpiprt4 at acpi0: bus -1 (PCE4)
> > acpiprt5 at acpi0: bus -1 (PCE5)
> > acpiprt6 at acpi0: bus -1 (PCE6)
> > acpiprt7 at acpi0: bus -1 (PCE7)
> > acpiprt8 at acpi0: bus -1 (PCE9)
> > acpiprt9 at acpi0: bus 2 (PCEA)
> > acpiprt10 at acpi0: bus -1 (PCEB)
> > acpiprt11 at acpi0: bus -1 (PCEC)
> > acpiprt12 at acpi0: bus 1 (AGP_)
> > acpicpu0 at acpi0: C1(@1 halt!), PSS
> > acpicpu1 at acpi0: C1(@1 halt!), PSS
> > acpibtn0 at acpi0: PWRB
> > acpicmos0 at acpi0
> > "PNP0C14" at acpi0 not configured
> > cpu0: PowerNow! K8 2505 MHz: speeds: 2500 2400 2200 2000 1800 1000 MHz
> > pci0 at mainbus0 bus 0
> > 0:0:0: mem address conflict 0xe0000000/0x20000000
> > pchb0 at pci0 dev 0 function 0 "AMD RS780 Host" rev 0x00
> > ppb0 at pci0 dev 1 function 0 "AMD RS780 PCIE" rev 0x00
> > pci1 at ppb0 bus 1
> > radeondrm0 at pci1 dev 5 function 0 "ATI Radeon HD 3200" rev 0x00
> > drm0 at radeondrm0
> > radeondrm0: apic 2 int 18
> > azalia0 at pci1 dev 5 function 1 "ATI RS780 HD Audio" rev 0x00: msi
> > azalia0: no supported codecs
> > ppb1 at pci0 dev 10 function 0 "AMD RS780 PCIE" rev 0x00: msi
> > pci2 at ppb1 bus 2
> > re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x02: RTL8168C/8111C (0x3c0=
> > 0), msi, address 00:1f:d0:86:00:60
> > rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 2
> > ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x00: apic 2 int 22, A=
> > HCI 1.1
> > ahci0: port 0: 3.0Gb/s
> > ahci0: port 2: 3.0Gb/s
> > scsibus1 at ahci0: 32 targets
> > sd0 at scsibus1 targ 0 lun 0: <ATA, Hitachi HDP72503, GM3O> SCSI3 0/direct =
> > fixed naa.5000cca34ddd54e3
> > sd0: 305244MB, 512 bytes/sector, 625140335 sectors
> > sd1 at scsibus1 targ 2 lun 0: <ATA, Hitachi HDP72503, GM3O> SCSI3 0/direct =
> > fixed naa.5000cca34ddd0950
> > sd1: 305244MB, 512 bytes/sector, 625140335 sectors
> > ohci0 at pci0 dev 18 function 0 "ATI SB700 USB" rev 0x00: apic 2 int 16, ve=
> > rsion 1.0, legacy support
> > ohci1 at pci0 dev 18 function 1 "ATI SB700 USB" rev 0x00: apic 2 int 16, ve=
> > rsion 1.0, legacy support
> > ehci0 at pci0 dev 18 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 17
> > usb0 at ehci0: USB revision 2.0
> > uhub0 at usb0 configuration 1 interface 0 "ATI EHCI root hub" rev 2.00/1.00=
> >  addr 1
> > ohci2 at pci0 dev 19 function 0 "ATI SB700 USB" rev 0x00: apic 2 int 18, ve=
> > rsion 1.0, legacy support
> > ohci2: SMM does not respond, will reset
> > ohci3 at pci0 dev 19 function 1 "ATI SB700 USB" rev 0x00: apic 2 int 18, ve=
> > rsion 1.0, legacy support
> > ehci1 at pci0 dev 19 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 19
> > usb1 at ehci1: USB revision 2.0
> > uhub1 at usb1 configuration 1 interface 0 "ATI EHCI root hub" rev 2.00/1.00=
> >  addr 1
> > piixpm0 at pci0 dev 20 function 0 "ATI SBx00 SMBus" rev 0x3a: SMI
> > iic0 at piixpm0
> > spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-6400CL5
> > spdmem1 at iic0 addr 0x51: 1GB DDR2 SDRAM non-parity PC2-6400CL5
> > spdmem2 at iic0 addr 0x52: 1GB DDR2 SDRAM non-parity PC2-6400CL6
> > spdmem3 at iic0 addr 0x53: 1GB DDR2 SDRAM non-parity PC2-6400CL6
> > pciide0 at pci0 dev 20 function 1 "ATI SB700 IDE" rev 0x00: DMA, channel 0 =
> > configured to compatibility, channel 1 configured to compatibility
> > atapiscsi0 at pciide0 channel 1 drive 0
> > scsibus2 at atapiscsi0: 2 targets
> > cd0 at scsibus2 targ 0 lun 0: <ATAPI, iHAS124 C, LL0E> ATAPI 5/cdrom remova=
> > ble
> > cd0(pciide0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5
> > pcib0 at pci0 dev 20 function 3 "ATI SB700 ISA" rev 0x00
> > ppb2 at pci0 dev 20 function 4 "ATI SB600 PCI" rev 0x00
> > pci3 at ppb2 bus 3
> > envy0 at pci3 dev 7 function 0 "IC Ensemble Envy24 I/O Ctrlr" rev 0x02: api=
> > c 2 int 21
> > envy0: M-Audio Audiophile 2496, 2 inputs, 2 outputs
> > audio0 at envy0
> > midi0 at envy0: <Envy24 MIDI UART>
> > "TI TSB43AB23 FireWire" rev 0x00 at pci3 dev 14 function 0 not configured
> > ohci4 at pci0 dev 20 function 5 "ATI SB700 USB" rev 0x00: apic 2 int 18, ve=
> > rsion 1.0, legacy support
> > pchb1 at pci0 dev 24 function 0 "AMD AMD64 0Fh HyperTransport" rev 0x00
> > pchb2 at pci0 dev 24 function 1 "AMD AMD64 0Fh Address Map" rev 0x00
> > pchb3 at pci0 dev 24 function 2 "AMD AMD64 0Fh DRAM Cfg" rev 0x00
> > kate0 at pci0 dev 24 function 3 "AMD AMD64 0Fh Misc Cfg" rev 0x00: core rev=
> >  BH-G2
> > usb2 at ohci0: USB revision 1.0
> > uhub2 at usb2 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
> >  addr 1
> > usb3 at ohci1: USB revision 1.0
> > uhub3 at usb3 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
> >  addr 1
> > usb4 at ohci2: USB revision 1.0
> > uhub4 at usb4 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
> >  addr 1
> > usb5 at ohci3: USB revision 1.0
> > uhub5 at usb5 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
> >  addr 1
> > isa0 at pcib0
> > isadma0 at isa0
> > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> > pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> > pckbd0 at pckbc0 (kbd slot)
> > wskbd0 at pckbd0: console keyboard
> > pms0 at pckbc0 (aux slot)
> > wsmouse0 at pms0 mux 0
> > pcppi0 at isa0 port 0x61
> > spkr0 at pcppi0
> > lpt0 at isa0 port 0x378/4 irq 7
> > it0 at isa0 port 0x2e/2: IT8718F rev 5, EC port 0x228
> > usb6 at ohci4: USB revision 1.0
> > uhub6 at usb6 configuration 1 interface 0 "ATI OHCI root hub" rev 1.00/1.00=
> >  addr 1
> > vmm0 at mainbus0: SVM
> > ugen0 at uhub3 port 1 "Ultima USB Scanner" rev 1.10/1.00 addr 2
> > vscsi0 at root
> > scsibus3 at vscsi0: 256 targets
> > softraid0 at root
> > scsibus4 at softraid0: 256 targets
> > root on sd0a (d62a14d69a338a1c.a) swap on sd0b dump on sd0b
> > initializing kernel modesetting (RS780 0x1002:0x9610 0x1458:0xD000).
> > radeondrm0: 1440x900, 32bpp
> > wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0
> > wsdisplay0: screen 1-5 added (std, vt100 emulation)
> > ulpt0 at uhub0 port 3 configuration 1 interface 0 "Brother HL-5250DN" rev 2=
> > =2E00/1.00 addr 2
> > ulpt0: using bi-directional mode
> >
>

Reply | Threaded
Open this post in threaded view
|

Re: amd64 cc error unknown argument '-msave-args'

John Rigg
In reply to this post by Theo de Raadt-2
On Sun, Feb 03, 2019 at 02:51:08PM -0700, Theo de Raadt wrote:
> John Rigg <[hidden email]> wrote:
>
> > I'm trying to compile a GENERIC.MP kernel on amd64
> > 6.4 -stable.
>
> No way, you are not.  Only -current has that, as of a few days ago.

I used the wrong cvs command and didn't spot it. Stupid mistake.
Sorry for the noise.

John

Reply | Threaded
Open this post in threaded view
|

Re: amd64 cc error unknown argument '-msave-args'

Jyri Hovila [Turvamies.fi]
In reply to this post by Theo de Raadt-2

> And since you are doing this with -current *ALL OVER THE PLACE*
> there are instructions that if you have trouble you should upgrade
> to a snapshot.

Theo, with all due respect, there are many situations where upgrading to a snapshot really isn't an option.

> Those instructions to exist the noise on the list everytime we
> make a change and people don't notice or understand it and suddenly
> they are in over their heads

Again with all due respect, should all users of OpenBSD constantly watch the development in order to be able to use it?

Yes, I know: the CURRENT is not for production use, etc. etc. etc.

Then again: using RELEASE is a huge pain from the perspective of a server administrator with many [often virtual] hosts to maintain. The pain is so big that it actually drove me away from using OpenBSD for almost a decade.

> *even our own developers* have to do that, from time to time

I'd say issues like this are the ones that prevent OpenBSD from being embraced by many otherwise potential users.

It's your project and you're free to handle it as you will. You're world famoous for "being difficult" in the sense that you don't seem to much care about the opinions and experiences of the "normal" users, so it obviously doesn't make sense to try and convert you from that -- that attitude is almost as part of the trademark already.

I must ask though: is it really so difficult to at least try and help people out, instead of lashing them?

I'd like to keep using OpenBSD, but I keep getting headaches due to the "stick it up yours" attitude when problems arise.

John, I'm getting the same problem with the amd64 version of CURRENT. Updating to a snapshot is not an option in my scenario, so I'll try and figure out how to get past the issue.

Theo, I honestly do appreciate you and the work you've done not just for OpenBSD but also OpenSSH etc. I just can't understand why you're ruining the [also commercial] potential by ignoring the needs of the users and by being so god damn hostile against pretty much anyone who's not willing to humbly submit to your idea of how things should be done.

-j.

Reply | Threaded
Open this post in threaded view
|

Re: amd64 cc error unknown argument '-msave-args'

Peter J. Philipp-3
On Tue, Feb 05, 2019 at 07:23:59AM +0200, Jyri Hovila [Turvamies.fi] wrote:

>
> > And since you are doing this with -current *ALL OVER THE PLACE*
> > there are instructions that if you have trouble you should upgrade
> > to a snapshot.
>
> Theo, with all due respect, there are many situations where upgrading to a snapshot really isn't an option.
>
> > Those instructions to exist the noise on the list everytime we
> > make a change and people don't notice or understand it and suddenly
> > they are in over their heads
>
> Again with all due respect, should all users of OpenBSD constantly watch the development in order to be able to use it?

I watch the source changes with great interest sometimes and with lesser
interest other times.  Sometimes life happens and it just flies past me,
but other times I'm grateful that I watched source changes.  

What I like particularily is well-written commit messages that give me a
good idea what the change was without having to go back to cvsweb to see
the actual change.  Theo is probably _the_ person with the best described
messages, and i put trust in those messages.

I ask you, if I can read source changes, why can't you?  I'm only a user
as well.

> Yes, I know: the CURRENT is not for production use, etc. etc. etc.
>
> Then again: using RELEASE is a huge pain from the perspective of a server administrator with many [often virtual] hosts to maintain. The pain is so big that it actually drove me away from using OpenBSD for almost a decade.
>
> > *even our own developers* have to do that, from time to time
>
> I'd say issues like this are the ones that prevent OpenBSD from being embraced by many otherwise potential users.
>
> It's your project and you're free to handle it as you will. You're world famoous for "being difficult" in the sense that you don't seem to much care about the opinions and experiences of the "normal" users, so it obviously doesn't make sense to try and convert you from that -- that attitude is almost as part of the trademark already.
>
> I must ask though: is it really so difficult to at least try and help people out, instead of lashing them?
>
> I'd like to keep using OpenBSD, but I keep getting headaches due to the "stick it up yours" attitude when problems arise.

I didn't get the feeling that the devs have this attitude.  Everyone is human
everyone has a bad day, and you must realise that developers have bigger
problems that we, the users, are let in on.  They are after all able to
meet regularily around the globe and identify the problems as well as ponder
about how to solve them.

> John, I'm getting the same problem with the amd64 version of CURRENT. Updating to a snapshot is not an option in my scenario, so I'll try and figure out how to get past the issue.
>
> Theo, I honestly do appreciate you and the work you've done not just for OpenBSD but also OpenSSH etc. I just can't understand why you're ruining the [also commercial] potential by ignoring the needs of the users and by being so god damn hostile against pretty much anyone who's not willing to humbly submit to your idea of how things should be done.
>
> -j.

I understand that OpenBSD is in it for themselves.  Us, the users who
follow the development do so for self-interest, and sometimes we get the
same result as the devs and we didn't do anything for that.  I find your
words to Theo somewhat pushy on a whole community, hence I'm writing this
to you.  It's just an instance where I don't agree, I like reading source
changes.

Regards,
-peter

Reply | Threaded
Open this post in threaded view
|

Re: amd64 cc error unknown argument '-msave-args'

Anthony J. Bentley-4
In reply to this post by Jyri Hovila [Turvamies.fi]
Jyri Hovila [Turvamies.fi] writes:
> Theo, with all due respect, there are many situations where upgrading
> to a snapshot really isn't an option.

In such a situation, you shouldn't expect to be able to build -current
all the time. And the advice you'll always get is: update to a snapshot,
because that makes the build problems magically go away.

> > Those instructions to exist the noise on the list everytime we
> > make a change and people don't notice or understand it and suddenly
> > they are in over their heads
>
> Again with all due respect, should all users of OpenBSD constantly watch the
> development in order to be able to use it?

The point of upgrading to a snapshot before building -current is you
don't have to be intimately familiar with what's going on in -current
that might affect a build.

> Then again: using RELEASE is a huge pain from the perspective of a server adm
> inistrator with many [often virtual] hosts to maintain. The pain is so big th
> at it actually drove me away from using OpenBSD for almost a decade.

This thread started with someone mistakenly building -current from
-stable. The OP intended to build -stable from -stable. The solution is
simple and documented: build -stable from -stable, build -current from
a snapshot, or even better, don't install from source if you can help it.

Is your suggestion that OpenBSD focus development effort on making it
possible to build -current from any conceivable post-6.4 checkout?
That seems an impossible task, one that would take time away from other
development efforts. Once again, the alternative is simple and well
documented: build -stable from -stable, build -current from snaps.

--
Anthony J. Bentley

Reply | Threaded
Open this post in threaded view
|

Re: amd64 cc error unknown argument '-msave-args'

John Rigg
In reply to this post by Jyri Hovila [Turvamies.fi]
On Tue, Feb 05, 2019 at 07:23:59AM +0200, Jyri Hovila [Turvamies.fi] wrote:
> I must ask though: is it really so difficult to at least
> try and help people out, instead of lashing them?

As the OP I found the replies to my post helpful. I made
a mistake (missed out the release tag on the cvs command
when trying to update to -stable) and the replies immediately
alerted me to the problem.

> Then again: using RELEASE is a huge pain from the
> perspective of a server administrator with many [often
> virtual] hosts to maintain. The pain is so big that it
> actually drove me away from using OpenBSD for almost a
> decade.

Syspatch and the existence of third-party packagers like
m:tier have made it much less painful. Meanwhile, other
OS's, eg. Systemd/Linux, have become much more painful
(I say this after 20 years of Linux use).

John

Reply | Threaded
Open this post in threaded view
|

Re: amd64 cc error unknown argument '-msave-args'

Theo de Raadt-2
In reply to this post by Jyri Hovila [Turvamies.fi]
Jyri Hovila [Turvamies.fi] <[hidden email]> wrote:

> > And since you are doing this with -current *ALL OVER THE PLACE*
> > there are instructions that if you have trouble you should upgrade
> > to a snapshot.
>
> Theo, with all due respect, there are many situations where upgrading to a snapshot really isn't an option.

Jyri,

That is incorrect.  The use of -current is "developer participation".
Snapshots are part of the developer "conversation".  They are built to
ensure we aren't making mistakes, and to help get over the hump when we
introduce incompatibilities which prevent build-over.  Many of the peopl
using them are testers helping ensure our FUTURE CODE DROP TO USERS --
which we release -- are in good shape.

RELEASES are used by "users".

SNAPSHOTS are used by developers, or people helping the development process.

These usage patterns are DISTINCT.

Everything you are saying is your DESIRE TO IMPOSE A DIFFERENT PROCESS
upon the developers, which is about 100 people already doing a hard
task, unlike you -- who are here carrying only "an opinion".

> > Those instructions to exist the noise on the list everytime we
> > make a change and people don't notice or understand it and suddenly
> > they are in over their heads
>
> Again with all due respect, should all users of OpenBSD constantly
> watch the development in order to be able to use it?
>
> Yes, I know: the CURRENT is not for production use, etc. etc. etc.

So you know the difference, but you wish to preach to us that we should
completely change our development process.

You really should just shut up.

> Then again: using RELEASE is a huge pain from the perspective of a
> server administrator with many [often virtual] hosts to maintain. The
> pain is so big that it actually drove me away from using OpenBSD for
> almost a decade.

Yes, life is hard.  Grow up or run something else.

> > *even our own developers* have to do that, from time to time
>
> I'd say issues like this are the ones that prevent OpenBSD from being
> embraced by many otherwise potential users.

You are allowed to have incorrect opinions which don't matter to us,
but preaching to us is quite impolite.


Reply | Threaded
Open this post in threaded view
|

Re: amd64 cc error unknown argument '-msave-args'

Theo de Raadt-2
In reply to this post by Anthony J. Bentley-4
Anthony J. Bentley <[hidden email]> wrote:

> Once again, the alternative is simple and well
> documented: build -stable from -stable, build -current from snaps.

Well said.