Re: reinstate xscreensaver desktop files and resolve conflict with mate-screensaver
ok for me
On 08/12/18 16:35 +0100, Landry Breuil wrote:
> Hi,
>
> xfce4-screensaver (as a fork of mate-screensaver) can make use of
> xscreensavers if available, but only if the desktop files are provided
> by xscreensaver.
>
> They were removed from xscreensaver in
> https://github.com/openbsd/ports/commit/aca4d39d8b5fcecb58e12320be0ac983d0134ae5#diff-23f2811b8a1d1d05717bfc412b99bc66
> because gnome-screensaver had been removed, but i think they can be
> reinstated as they can be used/listed as available by mate-screensaver &
> xfce4-screensaver. No need to add a RDEP on xscreensaver though.
> I looked and most linux distros ship those .desktop files too.
>
> While here install popsquares.desktop from mate as
> mate-popsquares.desktop so that it doesnt conflict with the one from
> xscreensaver - no need to rename the binary as its installed in a
> distinct dir. xfce4-screensaver installs xfce4-popsquares.desktop.
> On this point for example, debian's xscreensaver doesnt ship popsquares
> since
> https://salsa.debian.org/debian/xscreensaver/commit/3418b1b065fa32b02a0ee58308a6dea920af0220
>
> ok ?
> Index: Makefile
> ===
> RCS file: /cvs/ports/x11/mate/screensaver/Makefile,v
> retrieving revision 1.10
> diff -u -r1.10 Makefile
> --- Makefile 22 Sep 2018 06:08:03 - 1.10
> +++ Makefile 8 Dec 2018 12:10:08 -
> @@ -5,7 +5,7 @@
> MATE_PROJECT=mate-screensaver
> MATE_VERSION=1.20.2
>
> -REVISION=0
> +REVISION=1
>
> # LGPLv2
> PERMIT_PACKAGE_CDROM=Yes
> @@ -46,5 +46,6 @@
> post-install:
> @mv ${WRKINST}/etc/xdg/autostart \
> ${PREFIX}/share/examples/mate-screensaver/xdg/autostart
> + @mv ${PREFIX}/share/applications/screensavers/{,mate-}popsquares.desktop
>
> .include
> Index: pkg/PLIST
> ===
> RCS file: /cvs/ports/x11/mate/screensaver/pkg/PLIST,v
> retrieving revision 1.4
> diff -u -r1.4 PLIST
> --- pkg/PLIST 20 Sep 2018 11:16:44 - 1.4
> +++ pkg/PLIST 8 Dec 2018 12:10:08 -
> @@ -19,8 +19,8 @@
> share/applications/screensavers/cosmos-slideshow.desktop
> share/applications/screensavers/footlogo-floaters.desktop
> share/applications/screensavers/gnomelogo-floaters.desktop
> +share/applications/screensavers/mate-popsquares.desktop
> share/applications/screensavers/personal-slideshow.desktop
> -share/applications/screensavers/popsquares.desktop
> share/backgrounds/
> share/backgrounds/cosmos/
> share/backgrounds/cosmos/background-1.xml
> Index: Makefile
> ===
> RCS file: /cvs/ports/x11/xscreensaver/Makefile,v
> retrieving revision 1.98
> diff -u -r1.98 Makefile
> --- Makefile 13 Aug 2018 18:53:50 - 1.98
> +++ Makefile 8 Dec 2018 12:10:39 -
> @@ -4,6 +4,7 @@
>
> # XXX x11/kde4/artwork plist may need regen if an update adds a new hack.
> DISTNAME=xscreensaver-5.40
> +REVISION=0
>
> CATEGORIES= x11
>
> @@ -57,5 +58,16 @@
> .for i in deco circuit
> mv ${PREFIX}/man/man6/$i.6 ${PREFIX}/man/man6/xscreensaver-$i.6
> .endfor
> +# create dot.desktop files from xscreensaver xml files for use
> +# by freedesktop compliant screensavers
> + cp ${FILESDIR}/migrate-xscreensaver-config.sh ${WRKSRC}/hacks/config
> + cp ${FILESDIR}/xscreensaver-config.xsl ${WRKSRC}/hacks/config
> + cd ${WRKSRC}/hacks/config && \
> + for i in ${WRKSRC}/hacks/config/*.xml; do \
> + /bin/sh migrate-xscreensaver-config.sh $${i} ; done
> + ${INSTALL_DATA_DIR} ${PREFIX}/share/applications/screensavers/
> + ${INSTALL_DATA} ${WRKSRC}/hacks/config/*.desktop \
> + ${PREFIX}/share/applications/screensavers/
> +
>
> .include
> Index: pkg/PLIST
> ===
> RCS file: /cvs/ports/x11/xscreensaver/pkg/PLIST,v
> retrieving revision 1.45
> diff -u -r1.45 PLIST
> --- pkg/PLIST 13 Aug 2018 18:53:50 - 1.45
> +++ pkg/PLIST 8 Dec 2018 12:10:39 -
> @@ -489,6 +489,263 @@
> @man man/man6/xscreensaver-gl-helper.6
> @man man/man6/xspirograph.6
> @man man/man6/zoom.6
> +share/applications/screensavers/
> +share/applications/screensavers/abstractile.desktop
> +share/applications/screensavers/anemone.desktop
> +share/applications/screensavers/anemotaxis.desktop
> +share/applications/screensavers/ant.desktop
> +share/applications/screensavers/antinspect.desktop
> +share/applications/screensavers/antmaze.desktop
> +share/applications/screensavers/antspotlight.desktop
> +share/applications/screensavers/apollonian.desktop
> +share/applications/screensavers/apple2.desktop
> +share/applications/screensavers/atlantis.desktop
> +share/applications/screensavers/attraction.desktop
> +share/applications/screensavers/atunnel.desktop
> +share/applications/screens
sparc64 bulk build report
bulk build on sparc64-1.ports.openbsd.org started on Sat Dec 1 02:56:11 MST 2018 finished at Sun Dec 9 02:57:41 MST 2018 lasted 08D17h01m done with kern.version=OpenBSD 6.4-current (GENERIC) #46: Fri Nov 30 19:17:30 MST 2018 built packages:7524 Dec 1:416 Dec 2:154 Dec 3:125 Dec 4:73 Dec 5:118 Dec 6:471 Dec 7:804 Dec 8:4012 Dec 9:1350 critical path missing pkgs: http://build-failures.rhaalovely.net//sparc64/2018-12-01/summary.log build failures: 51 http://build-failures.rhaalovely.net//sparc64/2018-12-01/cad/qcad.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/cad/qucs.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/comms/fldigi.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/comms/hackrf.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/converters/lastools.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/devel/codeworker.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/devel/glog.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/devel/llvm,,-main.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/devel/physfs.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/devel/ptlib.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/devel/xtensa-elf/gcc.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/emulators/ppsspp.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/emulators/vice.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/games/dangerdeep.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/games/godot.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/games/hex-a-hop.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/games/late.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/games/prboom-plus.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/games/spacehulk.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/games/xevil.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/geo/py-fiona,python3.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/graphics/dcmtk.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/graphics/k3dsurf.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/graphics/makehuman.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/graphics/openexr-viewers.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/lang/apl.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/lang/freehdl.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/lang/gcc/6.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/lang/gerbil.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/mail/rspamd.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/math/gbc.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/net/megatools.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/net/mutella.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/net/pmacct.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/net/toxcore.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/net/valknut.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/net/xprobe.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/productivity/devtodo.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/security/sslscan,openssl.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/sysutils/atf-allwinner.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/telephony/pjsua,-main.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/textproc/libwpd.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/textproc/mupdf.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/www/dansguardian.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/www/havp.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/www/kore,pgsql.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/x11/blackbox.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/x11/treewm.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/x11/waimea.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/x11/wmi.log http://build-failures.rhaalovely.net//sparc64/2018-12-01/x11/xglobe,no_map.log recurrent failures failures/cad/qcad.log failures/cad/qucs.log failures/comms/hackrf.log failures/devel/codeworker.log failures/devel/glog.log failures/devel/physfs.log failures/devel/ptlib.log failures/devel/xtensa-elf/gcc.log failures/emulators/ppsspp.log failures/emulators/vice.log failures/games/dangerdeep.log failures/games/godot.log failures/games/hex-a-hop.log failures/games/late.log failures/games/prboom-plus.log failures/games/xevil.log failures/graphics/openexr-viewers.log failures/lang/apl.log failures/lang/freehdl.log failures/math/gbc.log failures/net/megatools.log failures/net/mutella.log failures/net/toxcore.log failures/net/valknu
Re: [update] sbcl-1.4.14
Josh Elsasser writes:
> On Mon, Dec 03, 2018 at 09:14:55AM +0200, Timo Myyrä wrote:
>> Hi,
>>
>> Here's an update to SBCL to bring it to latest version as I noticed the
>> release
>> fixes the thread support on OpenBSD.
>
> The recent release does indeed fix one threading problem, but
> unfortunately the sb-concurrency tests still hang for me on a
> quad-core machine.
>
> It is now possible to build the threads flavor on powerpc, but I'm not
> convinced that it's worth spending time on.
>
Yeah, the thread support seems to be restored in previous 'almost working' state
at least on amd64. Before 1.4.14 the concurrency tests failed always, now they
seem to pass so I guess it is same state as before.
>> This also changes the thread backend to futex and adds support for core
>> compression using zlib.
>
> Using futexes is probably a good idea, however I'd prefer to wait
> until any known issues with the portable pthreads backend are resolved
> first.
>
Good point.
>> I haven't tested this that much yet but tests seem to pass on amd64 at
>> least with it.
>
> As Solene noted, the build fails when clisp is used as the
> cross-compilation host. I've tracked down the breakage to sbcl
> revision 83bc16d48d70fdf1b1c0194a0e45753df1fbd480 but haven't made
> progress past that.
>
I did few test builds with sbcl releases and 1.4.8 was latest to compile,
compiling 1.4.9 already failed with clisp with similar message as the
1.4.14. Didn't have time yet to dig deeper myself.
>> Timo
>
> Further comments below.
>
>> Index: Makefile
>> ===
>> RCS file: /cvs/ports/lang/sbcl/Makefile,v
>> retrieving revision 1.38
>> diff -u -p -u -p -r1.38 Makefile
>> --- Makefile 24 Jun 2018 18:33:36 - 1.38
>> +++ Makefile 3 Dec 2018 07:06:41 -
>> @@ -6,7 +6,7 @@ USE_WXNEEDED = Yes
>>
>> COMMENT=compiler and runtime system for ANSI Common Lisp
>>
>> -V = 1.4.8
>> +V = 1.4.14
>> DISTNAME= sbcl-${V}-source
>> PKGNAME=sbcl-${V}
>> WRKDIST=${WRKDIR}/sbcl-${V}
>> @@ -21,7 +21,7 @@ PERMIT_PACKAGE_CDROM= Yes
>>
>> MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=sbcl/}
>>
>> -WANTLIB=c m util
>> +WANTLIB=c m util z
>>
>> PSEUDO_FLAVORS= native_bootstrap
>>
>> @@ -30,10 +30,10 @@ PSEUDO_FLAVORS= native_bootstrap
>> FLAVORS=threads
>> FLAVOR?=
>>
>> -EXTRA_PARAMS=
>> +EXTRA_PARAMS= --with-sb-core-compression
>> .if ${FLAVOR:Mthreads}
>> ONLY_FOR_ARCHS =amd64
>> -EXTRA_PARAMS+= --with-sb-thread
>> +EXTRA_PARAMS+= --with-sb-thread --with-sb-futex
>> WANTLIB+= pthread
>> .endif
>>
>> Index: distinfo
>> ===
>> RCS file: /cvs/ports/lang/sbcl/distinfo,v
>> retrieving revision 1.16
>> diff -u -p -u -p -r1.16 distinfo
>> --- distinfo 24 Jun 2018 18:33:36 - 1.16
>> +++ distinfo 3 Dec 2018 07:06:41 -
>> @@ -1,2 +1,2 @@
>> -SHA256 (sbcl-1.4.8-source.tar.bz2) =
>> ziS2K4hIJiHCKKT9bIAjUDMLYmPhsbmEYO60qB1/szU=
>> -SIZE (sbcl-1.4.8-source.tar.bz2) = 6040563
>> +SHA256 (sbcl-1.4.14-source.tar.bz2) =
>> TfJu1E1FWAzuy/nhpunkCV3nPHaZxrlFu+jMhxAwHCw=
>> +SIZE (sbcl-1.4.14-source.tar.bz2) = 6187821
>> Index: patches/patch-src_runtime_Config_generic-openbsd
>> ===
>> RCS file:
>> /cvs/ports/lang/sbcl/patches/patch-src_runtime_Config_generic-openbsd,v
>> retrieving revision 1.3
>> diff -u -p -u -p -r1.3 patch-src_runtime_Config_generic-openbsd
>> --- patches/patch-src_runtime_Config_generic-openbsd 8 Mar 2018 15:17:39
>> - 1.3
>> +++ patches/patch-src_runtime_Config_generic-openbsd 3 Dec 2018 07:06:41
>> -
>> @@ -12,12 +12,12 @@ Index: src/runtime/Config.generic-openbs
>> # provided with absolutely no warranty. See the COPYING and CREDITS
>> # files for more information.
>>
>> --LINKFLAGS += -export-dynamic -Wl,-z,wxneeded
>> +-LINKFLAGS += -Wl,-z,wxneeded
>> +LINKFLAGS += -Wl,--export-dynamic -Wl,-z,wxneeded
>
> This whole hunk can be dropped, another makefile fragment already adds
> -Wl,--export-dynamic
>
>> OS_LIBS += -lutil
>>
>> ifdef LISP_FEATURE_SB_THREAD
>> -@@ -17,9 +17,7 @@ CFLAGS += -pthread
>> +@@ -17,9 +17,7 @@ CFLAGS += -pthread -DOS_THREAD_STACK
>> OS_LIBS += -pthread
>> endif
>>
>> Index: patches/patch-src_runtime_GNUmakefile
>> ===
>> RCS file: /cvs/ports/lang/sbcl/patches/patch-src_runtime_GNUmakefile,v
>> retrieving revision 1.8
>> diff -u -p -u -p -r1.8 patch-src_runtime_GNUmakefile
>> --- patches/patch-src_runtime_GNUmakefile8 Mar 2018 15:17:39 -
>> 1.8
>> +++ patches/patch-src_runtime_GNUmakefile3 Dec 2018 07:06:41 -
>> @@ -2,7 +2,7 @@ $OpenBSD: patch-src_runtime_
owncloud removal?
Hi. So I am switching to nextcloud and will stop maintaining ownCloud. If anyone wants to keep maintaining it, be my guest, otherwise I'll remove it soon (unmaintained php apps are not sth we want...). I don't think it makes sense to have both apps in tree and the nextcloud README can be used to setup ownCloud from the official tarball as well so... -- Antoine
Update vmm-firmware port
I started looking at supporting fw_cfg in vmd. Now to make this work with
SeaBIOS there are a few fixes needed. First of all the way it reads the
FW_CFG_DATA port is not supported by vmm(4) (problem whith 'rep insb' on
IO ports). Additionally this cleans up some of the patches which I think
are not needed if the setting of screen-and-debug is changed. At least I
no longer see double printing of messages.
I enabled CONFIG_BOOTORDER because this is what I would like to tweak.
The CONFIG_DEBUG_LEVEL can be taken out before commit but it helped me
debugging this. Once vmd uses fw_cfg more of the patches can be removed.
--
:wq Claudio
Index: Makefile
===
RCS file: /cvs/ports/sysutils/firmware/vmm/Makefile,v
retrieving revision 1.15
diff -u -p -r1.15 Makefile
--- Makefile21 Nov 2018 00:26:05 - 1.15
+++ Makefile9 Dec 2018 11:09:05 -
@@ -13,7 +13,7 @@ CC = /usr/bin/gcc
FW_DRIVER= vmm
FW_VER=1.11.0
SB_VER=20100422
-REVISION= 0
+REVISION= 1
DISTNAME= seabios-${FW_VER}
DISTFILES= ${DISTNAME}${EXTRACT_SUFX} \
sgabios-20100422{23d474943dcd55d0550a3d20b3d30e9040a4f15b}.tar.gz:0
Index: files/config
===
RCS file: /cvs/ports/sysutils/firmware/vmm/files/config,v
retrieving revision 1.6
diff -u -p -r1.6 config
--- files/config11 Jul 2018 09:09:46 - 1.6
+++ files/config7 Dec 2018 20:34:05 -
@@ -15,7 +15,7 @@ CONFIG_QEMU_HARDWARE=y
# CONFIG_THREADS is not set
# CONFIG_RELOCATE_INIT is not set
# CONFIG_BOOTMENU is not set
-# CONFIG_BOOTORDER is not set
+CONFIG_BOOTORDER=y
# CONFIG_ENTRY_EXTRASTACK is not set
CONFIG_MALLOC_UPPERMEMORY=y
CONFIG_ROM_SIZE=0
@@ -92,7 +92,7 @@ CONFIG_VGA_EXTRA_STACK_SIZE=512
#
# Debugging
#
-CONFIG_DEBUG_LEVEL=-1
+CONFIG_DEBUG_LEVEL=1
CONFIG_DEBUG_SERIAL=y
CONFIG_DEBUG_SERIAL_PORT=0x3f8
CONFIG_DEBUG_IO=n
Index: patches/patch-src_boot_c
===
RCS file: patches/patch-src_boot_c
diff -N patches/patch-src_boot_c
--- patches/patch-src_boot_c11 Jul 2018 09:09:46 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,43 +0,0 @@
src/boot.c.origTue Jul 10 14:52:11 2018
-+++ src/boot.c Tue Jul 10 14:53:18 2018
-@@ -659,7 +659,7 @@ boot_cdrom(struct drive_s *drive)
- {
- if (! CONFIG_CDROM_BOOT)
- return;
--printf("Booting from DVD/CD...\n");
-+dprintf(1, "Booting from DVD/CD...\n");
-
- int status = cdrom_boot(drive);
- if (status) {
-@@ -685,7 +685,7 @@ boot_cbfs(struct cbfs_file *file)
- {
- if (!CONFIG_COREBOOT_FLASH)
- return;
--printf("Booting from CBFS...\n");
-+dprintf(1, "Booting from CBFS...\n");
- cbfs_run_payload(file);
- }
-
-@@ -693,7 +693,7 @@ boot_cbfs(struct cbfs_file *file)
- static void
- boot_rom(u32 vector)
- {
--printf("Booting from ROM...\n");
-+dprintf(1, "Booting from ROM...\n");
- struct segoff_s so;
- so.segoff = vector;
- call_boot_entry(so, 0);
-@@ -733,11 +733,11 @@ do_boot(int seq_nr)
- struct bev_s *ie = &BEV[seq_nr];
- switch (ie->type) {
- case IPL_TYPE_FLOPPY:
--printf("Booting from Floppy...\n");
-+dprintf(1, "Booting from Floppy...\n");
- boot_disk(0x00, CheckFloppySig);
- break;
- case IPL_TYPE_HARDDISK:
--printf("Booting from Hard Disk...\n");
-+dprintf(1, "Booting from Hard Disk...\n");
- boot_disk(0x80, 1);
- break;
- case IPL_TYPE_CDROM:
Index: patches/patch-src_fw_paravirt_c
===
RCS file: /cvs/ports/sysutils/firmware/vmm/patches/patch-src_fw_paravirt_c,v
retrieving revision 1.2
diff -u -p -r1.2 patch-src_fw_paravirt_c
--- patches/patch-src_fw_paravirt_c 26 Apr 2018 12:23:32 - 1.2
+++ patches/patch-src_fw_paravirt_c 9 Dec 2018 10:55:37 -
@@ -1,18 +1,27 @@
$OpenBSD: patch-src_fw_paravirt_c,v 1.2 2018/04/26 12:23:32 sthen Exp $
+Don't use 'rep insb' to read IO ports, vmm does not support that yet.
Allow detection of >4GB RAM. Normally seabios only allows this with the
qemu config device which VMM doesn't have.
Index: src/fw/paravirt.c
--- src/fw/paravirt.c.orig
+++ src/fw/paravirt.c
-@@ -500,6 +500,18 @@ qemu_cfg_e820(void)
- dprintf(1, "RamSizeOver4G: 0x%016llx [cmos]\n", RamSizeOver4G);
+@@ -257,7 +257,9 @@ qemu_cfg_read(void *buf, int len)
+ if (qemu_cfg_dma_enabled()) {
+ qemu_cfg_dma_transfer(buf, len, QEMU_CFG_DMA_CTL_READ);
+ } else {
+-insb(PORT_QEMU_CFG_DATA, buf, len);
++ u8 *d = buf;
++ while (len-- > 0)
++ *d++ = inb(PORT_QEMU_CFG_DATA);
+ }
}
-+void
-+vmm_check_high_mem(void)
-+{
+@@ -491,6 +493,18 @@ qemu_cfg_e820(void)
+ e820_add(0xfffbc000, 4*4096, E820_RESERVED);
+ }
+
+// Check for m
Re: Update vmm-firmware port
Hi,
I don’t understand - does this turn on more of these annoying debug messages
like “Boot from” by default again?
Reyk
> Am 09.12.2018 um 12:19 schrieb Claudio Jeker :
>
> I started looking at supporting fw_cfg in vmd. Now to make this work with
> SeaBIOS there are a few fixes needed. First of all the way it reads the
> FW_CFG_DATA port is not supported by vmm(4) (problem whith 'rep insb' on
> IO ports). Additionally this cleans up some of the patches which I think
> are not needed if the setting of screen-and-debug is changed. At least I
> no longer see double printing of messages.
> I enabled CONFIG_BOOTORDER because this is what I would like to tweak.
> The CONFIG_DEBUG_LEVEL can be taken out before commit but it helped me
> debugging this. Once vmd uses fw_cfg more of the patches can be removed.
>
> --
> :wq Claudio
>
> Index: Makefile
> ===
> RCS file: /cvs/ports/sysutils/firmware/vmm/Makefile,v
> retrieving revision 1.15
> diff -u -p -r1.15 Makefile
> --- Makefile21 Nov 2018 00:26:05 -1.15
> +++ Makefile9 Dec 2018 11:09:05 -
> @@ -13,7 +13,7 @@ CC =/usr/bin/gcc
> FW_DRIVER=vmm
> FW_VER=1.11.0
> SB_VER=20100422
> -REVISION=0
> +REVISION=1
> DISTNAME=seabios-${FW_VER}
> DISTFILES=${DISTNAME}${EXTRACT_SUFX} \
>sgabios-20100422{23d474943dcd55d0550a3d20b3d30e9040a4f15b}.tar.gz:0
> Index: files/config
> ===
> RCS file: /cvs/ports/sysutils/firmware/vmm/files/config,v
> retrieving revision 1.6
> diff -u -p -r1.6 config
> --- files/config11 Jul 2018 09:09:46 -1.6
> +++ files/config7 Dec 2018 20:34:05 -
> @@ -15,7 +15,7 @@ CONFIG_QEMU_HARDWARE=y
> # CONFIG_THREADS is not set
> # CONFIG_RELOCATE_INIT is not set
> # CONFIG_BOOTMENU is not set
> -# CONFIG_BOOTORDER is not set
> +CONFIG_BOOTORDER=y
> # CONFIG_ENTRY_EXTRASTACK is not set
> CONFIG_MALLOC_UPPERMEMORY=y
> CONFIG_ROM_SIZE=0
> @@ -92,7 +92,7 @@ CONFIG_VGA_EXTRA_STACK_SIZE=512
> #
> # Debugging
> #
> -CONFIG_DEBUG_LEVEL=-1
> +CONFIG_DEBUG_LEVEL=1
> CONFIG_DEBUG_SERIAL=y
> CONFIG_DEBUG_SERIAL_PORT=0x3f8
> CONFIG_DEBUG_IO=n
> Index: patches/patch-src_boot_c
> ===
> RCS file: patches/patch-src_boot_c
> diff -N patches/patch-src_boot_c
> --- patches/patch-src_boot_c11 Jul 2018 09:09:46 -1.1
> +++ /dev/null1 Jan 1970 00:00:00 -
> @@ -1,43 +0,0 @@
> src/boot.c.origTue Jul 10 14:52:11 2018
> -+++ src/boot.cTue Jul 10 14:53:18 2018
> -@@ -659,7 +659,7 @@ boot_cdrom(struct drive_s *drive)
> - {
> - if (! CONFIG_CDROM_BOOT)
> - return;
> --printf("Booting from DVD/CD...\n");
> -+dprintf(1, "Booting from DVD/CD...\n");
> -
> - int status = cdrom_boot(drive);
> - if (status) {
> -@@ -685,7 +685,7 @@ boot_cbfs(struct cbfs_file *file)
> - {
> - if (!CONFIG_COREBOOT_FLASH)
> - return;
> --printf("Booting from CBFS...\n");
> -+dprintf(1, "Booting from CBFS...\n");
> - cbfs_run_payload(file);
> - }
> -
> -@@ -693,7 +693,7 @@ boot_cbfs(struct cbfs_file *file)
> - static void
> - boot_rom(u32 vector)
> - {
> --printf("Booting from ROM...\n");
> -+dprintf(1, "Booting from ROM...\n");
> - struct segoff_s so;
> - so.segoff = vector;
> - call_boot_entry(so, 0);
> -@@ -733,11 +733,11 @@ do_boot(int seq_nr)
> - struct bev_s *ie = &BEV[seq_nr];
> - switch (ie->type) {
> - case IPL_TYPE_FLOPPY:
> --printf("Booting from Floppy...\n");
> -+dprintf(1, "Booting from Floppy...\n");
> - boot_disk(0x00, CheckFloppySig);
> - break;
> - case IPL_TYPE_HARDDISK:
> --printf("Booting from Hard Disk...\n");
> -+dprintf(1, "Booting from Hard Disk...\n");
> - boot_disk(0x80, 1);
> - break;
> - case IPL_TYPE_CDROM:
> Index: patches/patch-src_fw_paravirt_c
> ===
> RCS file: /cvs/ports/sysutils/firmware/vmm/patches/patch-src_fw_paravirt_c,v
> retrieving revision 1.2
> diff -u -p -r1.2 patch-src_fw_paravirt_c
> --- patches/patch-src_fw_paravirt_c26 Apr 2018 12:23:32 -1.2
> +++ patches/patch-src_fw_paravirt_c9 Dec 2018 10:55:37 -
> @@ -1,18 +1,27 @@
> $OpenBSD: patch-src_fw_paravirt_c,v 1.2 2018/04/26 12:23:32 sthen Exp $
>
> +Don't use 'rep insb' to read IO ports, vmm does not support that yet.
> Allow detection of >4GB RAM. Normally seabios only allows this with the
> qemu config device which VMM doesn't have.
>
> Index: src/fw/paravirt.c
> --- src/fw/paravirt.c.orig
> +++ src/fw/paravirt.c
> -@@ -500,6 +500,18 @@ qemu_cfg_e820(void)
> - dprintf(1, "RamSizeOver4G: 0x%016llx [cmos]\n", RamSizeOver4G);
> +@@ -257,7 +257,9 @@ qemu_cfg_read(void *buf, int len)
> + if (qemu_cfg_dma_enabled()) {
> + qemu_cfg_dma_transfer(buf, len, QE
Re: Update vmm-firmware port
On Sun, Dec 09, 2018 at 01:44:07PM +0100, Reyk Floeter wrote:
> Hi,
>
> I don’t understand - does this turn on more of these annoying debug
> messages like “Boot from” by default again?
>
If CONFIG_DEBUG_LEVEL is kept at -1 then the output will be:
Connected to /dev/ttypi (speed 115200)
Booting from Hard Disk...
Using drive 0, partition 3.
Loading..
probing: pc0 com0 mem[638K 510M a20=on]
disk: hd0+
>> OpenBSD/amd64 BOOT 3.41
-
com0: 115200 baud
switching console to com0
>> OpenBSD/amd64 BOOT 3.41
boot>
Since I plan to add bootorder support I think it is a useful message:
Connected to /dev/ttypi (speed 115200)
Booting from DVD/CD...
CD-ROM: E0
Loading /6.4/AMD64/CDBOOT
probing: pc0 com0 mem[638K 510M a20=on]
disk: hd0+ cd0
>> OpenBSD/amd64 CDBOOT 3.40
boot>
Makes it easier to know what SeaBIOS selected to boot from.
But honestly if this is the bikeshed to work on then I can readd the
boot.c diff since honestly that is absolutly unimportant.
> Reyk
>
> > Am 09.12.2018 um 12:19 schrieb Claudio Jeker :
> >
> > I started looking at supporting fw_cfg in vmd. Now to make this work with
> > SeaBIOS there are a few fixes needed. First of all the way it reads the
> > FW_CFG_DATA port is not supported by vmm(4) (problem whith 'rep insb' on
> > IO ports). Additionally this cleans up some of the patches which I think
> > are not needed if the setting of screen-and-debug is changed. At least I
> > no longer see double printing of messages.
> > I enabled CONFIG_BOOTORDER because this is what I would like to tweak.
> > The CONFIG_DEBUG_LEVEL can be taken out before commit but it helped me
> > debugging this. Once vmd uses fw_cfg more of the patches can be removed.
> >
> > --
> > :wq Claudio
> >
> > Index: Makefile
> > ===
> > RCS file: /cvs/ports/sysutils/firmware/vmm/Makefile,v
> > retrieving revision 1.15
> > diff -u -p -r1.15 Makefile
> > --- Makefile21 Nov 2018 00:26:05 -1.15
> > +++ Makefile9 Dec 2018 11:09:05 -
> > @@ -13,7 +13,7 @@ CC =/usr/bin/gcc
> > FW_DRIVER=vmm
> > FW_VER=1.11.0
> > SB_VER=20100422
> > -REVISION=0
> > +REVISION=1
> > DISTNAME=seabios-${FW_VER}
> > DISTFILES=${DISTNAME}${EXTRACT_SUFX} \
> >sgabios-20100422{23d474943dcd55d0550a3d20b3d30e9040a4f15b}.tar.gz:0
> > Index: files/config
> > ===
> > RCS file: /cvs/ports/sysutils/firmware/vmm/files/config,v
> > retrieving revision 1.6
> > diff -u -p -r1.6 config
> > --- files/config11 Jul 2018 09:09:46 -1.6
> > +++ files/config7 Dec 2018 20:34:05 -
> > @@ -15,7 +15,7 @@ CONFIG_QEMU_HARDWARE=y
> > # CONFIG_THREADS is not set
> > # CONFIG_RELOCATE_INIT is not set
> > # CONFIG_BOOTMENU is not set
> > -# CONFIG_BOOTORDER is not set
> > +CONFIG_BOOTORDER=y
> > # CONFIG_ENTRY_EXTRASTACK is not set
> > CONFIG_MALLOC_UPPERMEMORY=y
> > CONFIG_ROM_SIZE=0
> > @@ -92,7 +92,7 @@ CONFIG_VGA_EXTRA_STACK_SIZE=512
> > #
> > # Debugging
> > #
> > -CONFIG_DEBUG_LEVEL=-1
> > +CONFIG_DEBUG_LEVEL=1
> > CONFIG_DEBUG_SERIAL=y
> > CONFIG_DEBUG_SERIAL_PORT=0x3f8
> > CONFIG_DEBUG_IO=n
> > Index: patches/patch-src_boot_c
> > ===
> > RCS file: patches/patch-src_boot_c
> > diff -N patches/patch-src_boot_c
> > --- patches/patch-src_boot_c11 Jul 2018 09:09:46 -1.1
> > +++ /dev/null1 Jan 1970 00:00:00 -
> > @@ -1,43 +0,0 @@
> > src/boot.c.origTue Jul 10 14:52:11 2018
> > -+++ src/boot.cTue Jul 10 14:53:18 2018
> > -@@ -659,7 +659,7 @@ boot_cdrom(struct drive_s *drive)
> > - {
> > - if (! CONFIG_CDROM_BOOT)
> > - return;
> > --printf("Booting from DVD/CD...\n");
> > -+dprintf(1, "Booting from DVD/CD...\n");
> > -
> > - int status = cdrom_boot(drive);
> > - if (status) {
> > -@@ -685,7 +685,7 @@ boot_cbfs(struct cbfs_file *file)
> > - {
> > - if (!CONFIG_COREBOOT_FLASH)
> > - return;
> > --printf("Booting from CBFS...\n");
> > -+dprintf(1, "Booting from CBFS...\n");
> > - cbfs_run_payload(file);
> > - }
> > -
> > -@@ -693,7 +693,7 @@ boot_cbfs(struct cbfs_file *file)
> > - static void
> > - boot_rom(u32 vector)
> > - {
> > --printf("Booting from ROM...\n");
> > -+dprintf(1, "Booting from ROM...\n");
> > - struct segoff_s so;
> > - so.segoff = vector;
> > - call_boot_entry(so, 0);
> > -@@ -733,11 +733,11 @@ do_boot(int seq_nr)
> > - struct bev_s *ie = &BEV[seq_nr];
> > - switch (ie->type) {
> > - case IPL_TYPE_FLOPPY:
> > --printf("Booting from Floppy...\n");
> > -+dprintf(1, "Booting from Floppy...\n");
> > - boot_disk(0x00, CheckFloppySig);
> > - break;
> > - case IPL_TYPE_HARDDISK:
> > --printf("Booting from Hard Disk...\n");
> > -+dprintf(1, "Booting from Hard Disk...\n");
> > - boot_disk(0x80, 1);
> > - br
[update] productivity/tryton/5.0 - missing update in previous
Hi, Now tryton is linked in tree, portroach told me I missed one module in the previous maintenance update. So here a diff to update account_invoice module. All tests still passes. OK or comments ? -- Sebastien Marie Index: Makefile === RCS file: /cvs/ports/productivity/tryton/5.0/account_invoice/Makefile,v retrieving revision 1.1.1.1 diff -u -p -r1.1.1.1 Makefile --- Makefile3 Dec 2018 12:28:17 - 1.1.1.1 +++ Makefile9 Dec 2018 10:52:35 - @@ -1,6 +1,6 @@ # $OpenBSD: Makefile,v 1.1.1.1 2018/12/03 12:28:17 semarie Exp $ -MODPY_EGG_VERSION =5.0.0 +MODPY_EGG_VERSION =5.0.1 TRYTON_MODULE =account_invoice TRYTON_DEPENDS += account \ Index: distinfo === RCS file: /cvs/ports/productivity/tryton/5.0/account_invoice/distinfo,v retrieving revision 1.1.1.1 diff -u -p -r1.1.1.1 distinfo --- distinfo3 Dec 2018 12:28:17 - 1.1.1.1 +++ distinfo9 Dec 2018 10:52:40 - @@ -1,2 +1,2 @@ -SHA256 (tryton/trytond_account_invoice-5.0.0.tar.gz) = GZMtCiB6QgE02X4Ez1kqq6KzpPcO/OmoGAsb2dxzxxU= -SIZE (tryton/trytond_account_invoice-5.0.0.tar.gz) = 163181 +SHA256 (tryton/trytond_account_invoice-5.0.1.tar.gz) = yJzIgMgwooVzIT78dGHRucu/pRMT6JUKj4awB327hlU= +SIZE (tryton/trytond_account_invoice-5.0.1.tar.gz) = 163137
Re: [update] productivity/tryton/5.0 - missing update in previous
On Sun, Dec 09, 2018 at 02:27:56PM +0100, Sebastien Marie wrote: > Hi, > > Now tryton is linked in tree, portroach told me I missed one module in > the previous maintenance update. > > So here a diff to update account_invoice module. > > All tests still passes. > > OK or comments ? OK > -- > Sebastien Marie > > Index: Makefile > === > RCS file: /cvs/ports/productivity/tryton/5.0/account_invoice/Makefile,v > retrieving revision 1.1.1.1 > diff -u -p -r1.1.1.1 Makefile > --- Makefile 3 Dec 2018 12:28:17 - 1.1.1.1 > +++ Makefile 9 Dec 2018 10:52:35 - > @@ -1,6 +1,6 @@ > # $OpenBSD: Makefile,v 1.1.1.1 2018/12/03 12:28:17 semarie Exp $ > > -MODPY_EGG_VERSION = 5.0.0 > +MODPY_EGG_VERSION = 5.0.1 > TRYTON_MODULE = account_invoice > > TRYTON_DEPENDS +=account \ > Index: distinfo > === > RCS file: /cvs/ports/productivity/tryton/5.0/account_invoice/distinfo,v > retrieving revision 1.1.1.1 > diff -u -p -r1.1.1.1 distinfo > --- distinfo 3 Dec 2018 12:28:17 - 1.1.1.1 > +++ distinfo 9 Dec 2018 10:52:40 - > @@ -1,2 +1,2 @@ > -SHA256 (tryton/trytond_account_invoice-5.0.0.tar.gz) = > GZMtCiB6QgE02X4Ez1kqq6KzpPcO/OmoGAsb2dxzxxU= > -SIZE (tryton/trytond_account_invoice-5.0.0.tar.gz) = 163181 > +SHA256 (tryton/trytond_account_invoice-5.0.1.tar.gz) = > yJzIgMgwooVzIT78dGHRucu/pRMT6JUKj4awB327hlU= > +SIZE (tryton/trytond_account_invoice-5.0.1.tar.gz) = 163137 > -- Antoine
NEW: x11/kde-applications/spectacle
Information for inst:spectacle-18.08.2 Comment: KDE screen capture and screenshot program Description: Spectacle Spectacle is a simple application for capturing desktop screenshots. It can capture images of the entire desktop, a single monitor, the currently active window, the window currently under the mouse, or a rectangular region of the screen. The images can then be printed, sent to other applications for manipulation, or quickly be saved as-is. Features: - Capture the entire desktop (default) - Capture the current monitor - Capture the active window - Capture the window currently under the cursor, including parents of pop-up menus - Capture the window currently under the cursor, excluding parents of pop-up menus - Capture a rectangular region of the screen - Start in GUI mode (default) - Take a screenshot and exit without showing the GUI - Start in DBus-Activation mode - Save image to specified file in background mode - Wait for a click before taking screenshot Maintainer: KDE porting team WWW: https://www.kde.org/applications/graphics/spectacle/ I recently had to write a bug report for KDE5 dolphin on OpenBSD. I wanted to include a screenshot, so I needed a tool to do it. So here is spectacle which is a very handy tool to create screenshots and desktop records. Run-time test you can see here: https://bugsfiles.kde.org/attachment.cgi?id=116807 Ok to import? No conflicts with KDE4. Rafael Sadowski spectacle-18.08.2.tar.gz Description: Binary data
multimedia/mlt using frei0r-plugins
A few months ago, frei0r-plugins was posted to the list. By teaching
mlt to use these plugins, I can get kdenlive to do colour correction
properly. Enclosed is the patch to mlt so that it can use the proper
plugin values. (kdenlive needs no patch: it detects it via mlt.)
This requires the graphics/frei0r-plugins as earlier posted.
? mlt.frei0r.patch
Index: Makefile
===
RCS file: /cvs/ports/multimedia/mlt/Makefile,v
retrieving revision 1.17
diff -u -p -r1.17 Makefile
--- Makefile 29 Jul 2018 15:05:35 - 1.17
+++ Makefile 9 Dec 2018 14:14:33 -
@@ -55,6 +55,7 @@ LIB_DEPENDS-gpl2 = ${BUILD_PKGPATH},-mai
x11/qt5/qtsvg \
devel/sdl2 \
audio/libsamplerate \
+ graphics/frei0r-plugins \
graphics/libexif
MAKE_FLAGS = soversion=${LIBmlt_VERSION}
@@ -65,7 +66,6 @@ USE_GMAKE = Yes
CONFIGURE_STYLE = simple
CONFIGURE_ARGS = --mandir=${PREFIX}/man \
--disable-dv \
- --disable-frei0r \
--disable-kino \
--disable-swfdec \
--enable-gpl
Index: pkg/PLIST-gpl2
===
RCS file: /cvs/ports/multimedia/mlt/pkg/PLIST-gpl2,v
retrieving revision 1.3
diff -u -p -r1.3 PLIST-gpl2
--- pkg/PLIST-gpl2 29 Jul 2018 15:05:35 - 1.3
+++ pkg/PLIST-gpl2 9 Dec 2018 14:14:33 -
@@ -1,4 +1,5 @@
@comment $OpenBSD: PLIST-gpl2,v 1.3 2018/07/29 15:05:35 rsadowski Exp $
+lib/mlt/libmltfrei0r.so
lib/mlt/libmltlinsys.so
lib/mlt/libmltmotion_est.so
lib/mlt/libmltnormalize.so
@@ -8,6 +9,10 @@ lib/mlt/libmltresample.so
lib/mlt/libmltsdl2.so
lib/mlt/libmltvideostab.so
lib/mlt/libmltxine.so
+share/mlt/frei0r/
+share/mlt/frei0r/blacklist.txt
+share/mlt/frei0r/not_thread_safe.txt
+share/mlt/frei0r/param_name_map.yaml
share/mlt/linsys/
share/mlt/linsys/consumer_sdi.yml
share/mlt/motion_est/
Re: NEW: x11/kde-applications/spectacle
On Sun, Dec 09, 2018 at 02:40:19PM +0100, Rafael Sadowski wrote: > Description: > Spectacle Spectacle is a simple application for capturing desktop screenshots. ^ Twice With "Area: Rectengular Region" it dumps core when I click on "Take a new screenshot": $ /usr/ports/pobj/spectacle-18.08.2/build-amd64/src/spectacle QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kn' JIT is disabled for QML. Property bindings and animations will be very slow. Visit https://wiki.qt.io/V4 to learn about possible solutions for your platform. qrc:///QuickEditor/EditorRoot.qml:23:1: module "QtQuick.Controls" is not installed QObject::connect: Cannot connect (null)::acceptImage(int, int, int, int) to QuickEditor::acceptImageHandler(int, int, int, int) QObject::connect: Cannot connect (null)::cancelImage() to QuickEditor::grabCancelled() Segmentation fault (core dumped) $ egdb -se /usr/ports/pobj/spectacle-18.08.2/build-amd64/src/spectacle -c ./spectacle.core -batch -ex bt [New process 293943] [New process 238674] [New process 238227] [New process 414484] Core was generated by `spectacle'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0d7c59913242 in QObject::setProperty(char const*, QVariant const&) () from /usr/local/lib/libQt5Core.so.2.2 [Current thread is 1 (process 293943)] #0 0x0d7c59913242 in QObject::setProperty(char const*, QVariant const&) () from /usr/local/lib/libQt5Core.so.2.2 #1 0x0d79b50cd554 in QuickEditor::QuickEditor (this=0xd7c47b16560, pixmap=..., parent=0x0) at /usr/ports/pobj/spectacle-18.08.2/spectacle-18.08.2/src/QuickEditor/QuickEditor.cpp:117 #2 0x0d79b50d3c9f in X11ImageGrabber::grabRectangularRegion (this=0xd7c3f51e000) at /usr/ports/pobj/spectacle-18.08.2/spectacle-18.08.2/src/PlatformBackends/X11ImageGrabber.cpp:668 #3 0x0d79b50b0493 in ImageGrabber::doImageGrab (this=0xd7c3f51e000) at /usr/ports/pobj/spectacle-18.08.2/spectacle-18.08.2/src/PlatformBackends/ImageGrabber.cpp:100 #4 0x0d79b50a8fa6 in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (ImageGrabber::*)()>::call(void (ImageGrabber::*)(), ImageGrabber*, void**) (f=&virtual table offset 104, o=0xd7c3f51e000, arg=0x7f7ddab0) at /usr/local/include/X11/qt5/QtCore/qobjectdefs_impl.h:136 #5 0x0d79b50a8ef0 in QtPrivate::FunctionPointer::call, void>(void (ImageGrabber::*)(), ImageGrabber*, void**) (f=&virtual table offset 104, o=0xd7c3f51e000, arg=0x7f7ddab0) at /usr/local/include/X11/qt5/QtCore/qobjectdefs_impl.h:169 #6 0x0d79b50a8dd3 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0xd7bdd96fa60, r=0xd7c3f51e000, a=0x7f7ddab0, ret=0x0) at /usr/local/include/X11/qt5/QtCore/qobject_impl.h:120 #7 0x0d7c5991c2fb in QSingleShotTimer::timerEvent(QTimerEvent*) () from /usr/local/lib/libQt5Core.so.2.2 #8 0x0d7c5990af8e in QObject::event(QEvent*) () from /usr/local/lib/libQt5Core.so.2.2 #9 0x0d7c9ec9e4dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/local/lib/libQt5Widgets.so.2.2 #10 0x0d7c9ec9fad9 in QApplication::notify(QObject*, QEvent*) () from /usr/local/lib/libQt5Widgets.so.2.2 #11 0x0d7c598db9fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/local/lib/libQt5Core.so.2.2 #12 0x0d7c599387c6 in QTimerInfoList::activateTimers() () from /usr/local/lib/libQt5Core.so.2.2 #13 0x0d7c5993a84f in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/local/lib/libQt5Core.so.2.2 #14 0x0d7c52730099 in g_main_dispatch (context=) at gmain.c:3176 #15 g_main_context_dispatch (context=) at gmain.c:3829 #16 0x0d7c527304a3 in g_main_context_iterate (context=, block=, dispatch=, self=) at gmain.c:3902 #17 0x0d7c52730583 in g_main_context_iteration (context=0xd7c49dc9800, may_block=1) at gmain.c:3963 #18 0x0d7c59939a9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/local/lib/libQt5Core.so.2.2 #19 0x0d7c598d6dbe in QEventLoop::exec(QFlags) () from /usr/local/lib/libQt5Core.so.2.2 #20 0x0d7c598dc334 in QCoreApplication::exec() () from /usr/local/lib/libQt5Core.so.2.2 #21 0x0d79b509504b in main (argc=1, argv=0x7f7decc8) at /usr/ports/pobj/spectacle-18.08.2/spectacle-18.08.2/src/Main.cpp:157
Re: multimedia/mlt using frei0r-plugins
On Sun, Dec 09, 2018 at 03:17:33PM +0100, Kristaps Dzonsons wrote: > A few months ago, frei0r-plugins was posted to the list. By teaching > mlt to use these plugins, I can get kdenlive to do colour correction > properly. Enclosed is the patch to mlt so that it can use the proper > plugin values. (kdenlive needs no patch: it detects it via mlt.) Sounds legit and reads good except you're missing a REVISION bump. > This requires the graphics/frei0r-plugins as earlier posted. I haven't tested it.
NEW: p5-Rex
Hi, Following https://marc.info/?l=openbsd-ports&m=146753658609587&w=2, here is a port for p5-Rex. $ cat pkg/DESCR a command line tool which executes commands on remote servers. Define tasks in Perl and execute them on remote servers or groups of servers. Rex can be used to: _ Deploy web applications to servers sequentially or in parallel. _ Automate common tasks. _ Provision servers using Rex's builtin tools. It works great for me. I created some patches for the Pkg and the User module. I'll see to send them upstream. Feel free to test, comment, commit. Thanks, Best. -- Olivier Cherrier Phone: +352691754777 mailto:o...@symacx.com p5-Rex.tgz Description: application/tar-gz
Re: Update vmm-firmware port
> Am 09.12.2018 um 14:01 schrieb Claudio Jeker :
>
>> On Sun, Dec 09, 2018 at 01:44:07PM +0100, Reyk Floeter wrote:
>> Hi,
>>
>> I don’t understand - does this turn on more of these annoying debug
>> messages like “Boot from” by default again?
>>
>
> If CONFIG_DEBUG_LEVEL is kept at -1 then the output will be:
>
> Connected to /dev/ttypi (speed 115200)
> Booting from Hard Disk...
> Using drive 0, partition 3.
> Loading..
> probing: pc0 com0 mem[638K 510M a20=on]
> disk: hd0+
>>> OpenBSD/amd64 BOOT 3.41
> -
> com0: 115200 baud
> switching console to com0
>>> OpenBSD/amd64 BOOT 3.41
> boot>
>
> Since I plan to add bootorder support I think it is a useful message:
>
> Connected to /dev/ttypi (speed 115200)
> Booting from DVD/CD...
> CD-ROM: E0
> Loading /6.4/AMD64/CDBOOT
> probing: pc0 com0 mem[638K 510M a20=on]
> disk: hd0+ cd0
>>> OpenBSD/amd64 CDBOOT 3.40
> boot>
>
> Makes it easier to know what SeaBIOS selected to boot from.
> But honestly if this is the bikeshed to work on then I can readd the
> boot.c diff since honestly that is absolutly unimportant.
>
It’s not a bikeshed since I intentionally added this diff to remove the debug
messages before.
And we know from the later messages if it selected CDROM, HDD, etc. So please
keep the diff that removes it.
Otherwise OK reyk@
>> Reyk
>>
>>> Am 09.12.2018 um 12:19 schrieb Claudio Jeker :
>>>
>>> I started looking at supporting fw_cfg in vmd. Now to make this work with
>>> SeaBIOS there are a few fixes needed. First of all the way it reads the
>>> FW_CFG_DATA port is not supported by vmm(4) (problem whith 'rep insb' on
>>> IO ports). Additionally this cleans up some of the patches which I think
>>> are not needed if the setting of screen-and-debug is changed. At least I
>>> no longer see double printing of messages.
>>> I enabled CONFIG_BOOTORDER because this is what I would like to tweak.
>>> The CONFIG_DEBUG_LEVEL can be taken out before commit but it helped me
>>> debugging this. Once vmd uses fw_cfg more of the patches can be removed.
>>>
>>> --
>>> :wq Claudio
>>>
>>> Index: Makefile
>>> ===
>>> RCS file: /cvs/ports/sysutils/firmware/vmm/Makefile,v
>>> retrieving revision 1.15
>>> diff -u -p -r1.15 Makefile
>>> --- Makefile21 Nov 2018 00:26:05 -1.15
>>> +++ Makefile9 Dec 2018 11:09:05 -
>>> @@ -13,7 +13,7 @@ CC =/usr/bin/gcc
>>> FW_DRIVER=vmm
>>> FW_VER=1.11.0
>>> SB_VER=20100422
>>> -REVISION=0
>>> +REVISION=1
>>> DISTNAME=seabios-${FW_VER}
>>> DISTFILES=${DISTNAME}${EXTRACT_SUFX} \
>>> sgabios-20100422{23d474943dcd55d0550a3d20b3d30e9040a4f15b}.tar.gz:0
>>> Index: files/config
>>> ===
>>> RCS file: /cvs/ports/sysutils/firmware/vmm/files/config,v
>>> retrieving revision 1.6
>>> diff -u -p -r1.6 config
>>> --- files/config11 Jul 2018 09:09:46 -1.6
>>> +++ files/config7 Dec 2018 20:34:05 -
>>> @@ -15,7 +15,7 @@ CONFIG_QEMU_HARDWARE=y
>>> # CONFIG_THREADS is not set
>>> # CONFIG_RELOCATE_INIT is not set
>>> # CONFIG_BOOTMENU is not set
>>> -# CONFIG_BOOTORDER is not set
>>> +CONFIG_BOOTORDER=y
>>> # CONFIG_ENTRY_EXTRASTACK is not set
>>> CONFIG_MALLOC_UPPERMEMORY=y
>>> CONFIG_ROM_SIZE=0
>>> @@ -92,7 +92,7 @@ CONFIG_VGA_EXTRA_STACK_SIZE=512
>>> #
>>> # Debugging
>>> #
>>> -CONFIG_DEBUG_LEVEL=-1
>>> +CONFIG_DEBUG_LEVEL=1
>>> CONFIG_DEBUG_SERIAL=y
>>> CONFIG_DEBUG_SERIAL_PORT=0x3f8
>>> CONFIG_DEBUG_IO=n
>>> Index: patches/patch-src_boot_c
>>> ===
>>> RCS file: patches/patch-src_boot_c
>>> diff -N patches/patch-src_boot_c
>>> --- patches/patch-src_boot_c11 Jul 2018 09:09:46 -1.1
>>> +++ /dev/null1 Jan 1970 00:00:00 -
>>> @@ -1,43 +0,0 @@
>>> src/boot.c.origTue Jul 10 14:52:11 2018
>>> -+++ src/boot.cTue Jul 10 14:53:18 2018
>>> -@@ -659,7 +659,7 @@ boot_cdrom(struct drive_s *drive)
>>> - {
>>> - if (! CONFIG_CDROM_BOOT)
>>> - return;
>>> --printf("Booting from DVD/CD...\n");
>>> -+dprintf(1, "Booting from DVD/CD...\n");
>>> -
>>> - int status = cdrom_boot(drive);
>>> - if (status) {
>>> -@@ -685,7 +685,7 @@ boot_cbfs(struct cbfs_file *file)
>>> - {
>>> - if (!CONFIG_COREBOOT_FLASH)
>>> - return;
>>> --printf("Booting from CBFS...\n");
>>> -+dprintf(1, "Booting from CBFS...\n");
>>> - cbfs_run_payload(file);
>>> - }
>>> -
>>> -@@ -693,7 +693,7 @@ boot_cbfs(struct cbfs_file *file)
>>> - static void
>>> - boot_rom(u32 vector)
>>> - {
>>> --printf("Booting from ROM...\n");
>>> -+dprintf(1, "Booting from ROM...\n");
>>> - struct segoff_s so;
>>> - so.segoff = vector;
>>> - call_boot_entry(so, 0);
>>> -@@ -733,11 +733,11 @@ do_boot(int seq_nr)
>>> - struct bev_s *ie = &BEV[seq_nr];
>>> - switch (ie->type) {
>>> - case IPL_TYPE_FLOPPY:
>>> --p
Re: [update] devel/radare2 3.1.0
On Sun, Dec 09, 2018 at 05:36:21AM +, David CARLIER wrote: > Hi, > > there is an update for radare2 and radare2-bindings. Looks good diff-wise, but the build fails for me. (I don't have the old version installed) I'm running: OpenBSD 6.4-current (GENERIC.MP) #493: Wed Dec 5 22:00:48 MST 2018 ---8<--- ... gmake -C binr gmake[1]: Entering directory '/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/binr' gmake[2]: Entering directory '/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/binr/rax2' cc -c -O2 -pipe -O2 -pipe -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -I/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/libr/..//libr/include -o rax2.o rax2.c cc -O2 -pipe -O2 -pipe -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -I/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/libr/..//libr/include rax2.o -L.. -o rax2 -L/usr/local/lib -lpthread -lm -L/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/libr/util -lr_util -fPIC -lz -lzip /usr/bin/ld: error: undefined symbol: ret_ascii_table >>> referenced by rax2.c:75 >>> rax2.o:(rax) /usr/bin/ld: error: undefined symbol: r_hex_from_code >>> referenced by rax2.c:391 >>> rax2.o:(rax) /usr/bin/ld: error: undefined symbol: r_print_hex_from_bin >>> referenced by rax2.c:469 >>> rax2.o:(rax) cc: error: linker command failed with exit code 1 (use -v to see invocation) --->8--- -- Best Regards Edd Barrett http://www.theunixzoo.co.uk
Re: [update] sbcl-1.4.14
On Sun, Dec 09, 2018 at 12:20:09PM +0200, Timo Myyrä wrote:
[snip]
> >> I haven't tested this that much yet but tests seem to pass on amd64 at
> >> least with it.
> >
> > As Solene noted, the build fails when clisp is used as the
> > cross-compilation host. I've tracked down the breakage to sbcl
> > revision 83bc16d48d70fdf1b1c0194a0e45753df1fbd480 but haven't made
> > progress past that.
> >
>
> I did few test builds with sbcl releases and 1.4.8 was latest to compile,
> compiling 1.4.9 already failed with clisp with similar message as the
> 1.4.14. Didn't have time yet to dig deeper myself.
Now fixed in 3c15424ebc0f694108924ca5077a197783358920 upstream.
> Here's a new diff fixing some of the feedback.
>
> Compiles and compile tests pass on amd64 but when running actual tests 'make
> test' I get following:
> ::: UNEXPECTED-FAILURE :WITHOUT-INTERRUPTS+CONDITION-WAIT due to SIMPLE-ERROR:
> "The assertion (THREAD-ALIVE-P THREAD) failed with THREAD =
> #."
>
> and a bit later it gets stuck on:
> ::: Running :DEADLOCK-DETECTION.3
>
>
> What do you think about adding print/texinfo dependency and use it to generate
> the info file. It complains about unknown UTF-8 encoding during the makeinfo
> call:
I would prefer not to add such a large dependency unless it's
necessary. We used to do that and it was a burden when testing port
updates.
> /expanding variables in variables.texinfo
> /creating encodings.texi-temp
> makeinfo -I "docstrings/" -I "../../contrib/" asdf.texinfo
> asdf.texinfo:2219: warning: @strong{Note...} produces a spurious
> cross-reference in Info; reword to avoid that.
> asdf.texinfo:: warning: @strong{Note...} produces a spurious
> cross-reference in Info; reword to avoid that.
> makeinfo -I "docstrings/" -I "../../contrib/" sbcl.texinfo
> sbcl.texinfo:5: warning: unrecognized encoding name `UTF-8'.
>
> The ports versions should understand that but I'm not sure if the manuals
> contain stuff which really requires UTF-8 encoding..
>
> Once the clisp bootstrap is fixed the port would be ready for update without
> the
> futex stuff.
The rest looks fine as far as I can tell. I think you should send the
futex patch to the sbcl-devel list so someone more familiar with
sbcl's futex code can look at it.
> Timo
>
> Index: Makefile
> ===
> RCS file: /cvs/ports/lang/sbcl/Makefile,v
> retrieving revision 1.38
> diff -u -p -u -p -r1.38 Makefile
> --- Makefile 24 Jun 2018 18:33:36 - 1.38
> +++ Makefile 9 Dec 2018 10:04:13 -
> @@ -6,7 +6,7 @@ USE_WXNEEDED =Yes
>
> COMMENT= compiler and runtime system for ANSI Common Lisp
>
> -V = 1.4.8
> +V = 1.4.14
> DISTNAME=sbcl-${V}-source
> PKGNAME= sbcl-${V}
> WRKDIST= ${WRKDIR}/sbcl-${V}
> @@ -21,7 +21,7 @@ PERMIT_PACKAGE_CDROM= Yes
>
> MASTER_SITES=${MASTER_SITE_SOURCEFORGE:=sbcl/}
>
> -WANTLIB= c m util
> +WANTLIB= c m util z
>
> PSEUDO_FLAVORS= native_bootstrap
>
> @@ -30,7 +30,7 @@ PSEUDO_FLAVORS= native_bootstrap
> FLAVORS= threads
> FLAVOR?=
>
> -EXTRA_PARAMS=
> +EXTRA_PARAMS=--with-sb-core-compression
> .if ${FLAVOR:Mthreads}
> ONLY_FOR_ARCHS = amd64
> EXTRA_PARAMS+= --with-sb-thread --with-sb-futex
> Index: distinfo
> ===
> RCS file: /cvs/ports/lang/sbcl/distinfo,v
> retrieving revision 1.16
> diff -u -p -u -p -r1.16 distinfo
> --- distinfo 24 Jun 2018 18:33:36 - 1.16
> +++ distinfo 9 Dec 2018 10:04:13 -
> @@ -1,2 +1,2 @@
> -SHA256 (sbcl-1.4.8-source.tar.bz2) =
> ziS2K4hIJiHCKKT9bIAjUDMLYmPhsbmEYO60qB1/szU=
> -SIZE (sbcl-1.4.8-source.tar.bz2) = 6040563
> +SHA256 (sbcl-1.4.14-source.tar.bz2) =
> TfJu1E1FWAzuy/nhpunkCV3nPHaZxrlFu+jMhxAwHCw=
> +SIZE (sbcl-1.4.14-source.tar.bz2) = 6187821
> Index: patches/patch-src_runtime_Config_generic-openbsd
> ===
> RCS file:
> /cvs/ports/lang/sbcl/patches/patch-src_runtime_Config_generic-openbsd,v
> retrieving revision 1.3
> diff -u -p -u -p -r1.3 patch-src_runtime_Config_generic-openbsd
> --- patches/patch-src_runtime_Config_generic-openbsd 8 Mar 2018 15:17:39
> - 1.3
> +++ patches/patch-src_runtime_Config_generic-openbsd 9 Dec 2018 10:04:13
> -
> @@ -1,23 +1,11 @@
> $OpenBSD: patch-src_runtime_Config_generic-openbsd,v 1.3 2018/03/08 15:17:39
> sthen Exp $
>
> -clang-5.0.0 doesn't pass -export-dynamic to the linker, instead it
> -passes a bogus -e export-dynamic to ld(1). Just use -Wl,--export-dynamic.
> -
> Don't try to guess (wrong) with clang. Just assume we have pie
>
> Index: src/runtime/Config.generic-openbsd
> --- src/runtime/Config.generic-openbsd.orig
> +++ src/runtime/Config.generic-openbsd
> -@@
Re: [update] devel/radare2 3.1.0
I retested make package from a VM and still builds for me. Is not it the same issue than the last time ? On Sun, 9 Dec 2018 at 15:43, Edd Barrett wrote: > > On Sun, Dec 09, 2018 at 05:36:21AM +, David CARLIER wrote: > > Hi, > > > > there is an update for radare2 and radare2-bindings. > > Looks good diff-wise, but the build fails for me. > > (I don't have the old version installed) > > I'm running: > OpenBSD 6.4-current (GENERIC.MP) #493: Wed Dec 5 22:00:48 MST 2018 > > ---8<--- > ... > gmake -C binr > gmake[1]: Entering directory > '/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/binr' > gmake[2]: Entering directory > '/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/binr/rax2' > cc -c -O2 -pipe -O2 -pipe -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 > -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -O2 -pipe -MD -fPIC -g > -Wall -D__UNIX__=1 > -I/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/libr/..//libr/include -o > rax2.o rax2.c > cc -O2 -pipe -O2 -pipe -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -O2 > -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -O2 -pipe -MD -fPIC -g -Wall > -D__UNIX__=1 > -I/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/libr/..//libr/include > rax2.o -L.. -o rax2 -L/usr/local/lib -lpthread -lm > -L/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/libr/util -lr_util -fPIC > -lz -lzip > /usr/bin/ld: error: undefined symbol: ret_ascii_table > >>> referenced by rax2.c:75 > >>> rax2.o:(rax) > > /usr/bin/ld: error: undefined symbol: r_hex_from_code > >>> referenced by rax2.c:391 > >>> rax2.o:(rax) > > /usr/bin/ld: error: undefined symbol: r_print_hex_from_bin > >>> referenced by rax2.c:469 > >>> rax2.o:(rax) > cc: error: linker command failed with exit code 1 (use -v to see > invocation) > --->8--- > > -- > Best Regards > Edd Barrett > > http://www.theunixzoo.co.uk
Re: NEW: x11/kde-applications/kalzium
On Fri Nov 23, 2018 at 02:58:03PM +0100, Rafael Sadowski wrote: > > Information for inst:kalzium-18.08.2 > > Comment: > periodic table of elements > > Description: > Kalzium is your digital replacement for the periodic table on paper. It is a > program that visualizes the Periodic Table of Elements (PSE) and includes > basic > information about all common elements in the PSE. It has a gained much more > functions over time. > > Features > > - versatile overview of all important data from the elements like melting >points, electron affinity, electronegativity, electron configuration, > radii, >mass, ionisation energy > - tool to visualize the spectral lines of each element > - different colored views of the PSE: separation of the different blocks, > Year >simulator, Temperature simulator > - Molecular weight calculator > - an Isotope table > - 3D molecule editor, with a load and save functionality > - an equation solver for stoichiometric problems > - filetype conversion for different types of chemical programs > - tool to produce a comprehensive list of all Risk_and_Safety_Statements > > Maintainer: KDE porting team > > WWW: https://edu.kde.org/kalzium/ > > OK to import? KDE4 Kalzium was never ported to OpenBSD, so we see only > the standard conflicts with l10n. > > Rafael New tarball attached, includes a small tweak from landry@ and a completed LIB_DEPENDS. ok? kalzium-18.08.2p0.tar.gz Description: Binary data
UPDATE: devel/sdcc 3.7.0 => 3.8.0
Hi ports --
Attached is an update to SDCC.
I don't much use it any more, so testing appreciated.
Relevant changelog is here: http://sdcc.sourceforge.net/index.php#News
~Brian
Index: Makefile
===
RCS file: /cvs/ports/devel/sdcc/Makefile,v
retrieving revision 1.25
diff -u -p -r1.25 Makefile
--- Makefile 14 Nov 2018 20:48:21 - 1.25
+++ Makefile 9 Dec 2018 20:16:26 -
@@ -5,9 +5,8 @@ BROKEN-sparc64= illegal operands buildin
BROKEN-alpha= sdcc segfaults when building the device library
BROKEN-aarch64= *** BFD does not support target aarch64-unknown-openbsd6.2.
-DISTNAME= sdcc-src-3.7.0
+DISTNAME= sdcc-src-3.8.0
PKGNAME= ${DISTNAME:S/-src//}
-REVISION= 1
EXTRACT_SUFX= .tar.bz2
CATEGORIES= devel
@@ -16,7 +15,8 @@ MAINTAINER= Brian Callahan
Index: distinfo
===
RCS file: /cvs/ports/devel/sdcc/distinfo,v
retrieving revision 1.7
diff -u -p -r1.7 distinfo
--- distinfo 7 Mar 2018 21:34:43 - 1.7
+++ distinfo 9 Dec 2018 20:16:26 -
@@ -1,2 +1,2 @@
-SHA256 (sdcc-src-3.7.0.tar.bz2) = hU1HCUaYsGFC3z1fxka7VA1JerQHOtLwUbjsIUHflI4=
-SIZE (sdcc-src-3.7.0.tar.bz2) = 17944920
+SHA256 (sdcc-src-3.8.0.tar.bz2) = szFmjet72DLv0RIFLlsO0jE9tkGpIr05KAum1HrbuyE=
+SIZE (sdcc-src-3.8.0.tar.bz2) = 18987862
Index: patches/patch-sim_ucsim_cmd_src_Makefile_in
===
RCS file: /cvs/ports/devel/sdcc/patches/patch-sim_ucsim_cmd_src_Makefile_in,v
retrieving revision 1.1
diff -u -p -r1.1 patch-sim_ucsim_cmd_src_Makefile_in
--- patches/patch-sim_ucsim_cmd_src_Makefile_in 7 Mar 2018 21:34:43 - 1.1
+++ patches/patch-sim_ucsim_cmd_src_Makefile_in 9 Dec 2018 20:16:26 -
@@ -21,7 +21,7 @@ Index: sim/ucsim/cmd.src/Makefile.in
# My rules
#
-@@ -116,7 +116,7 @@ $(top_builddir)/libcmd.a: $(OBJECTS) $(LOCAL_OBJECTS)
+@@ -116,12 +116,12 @@ $(top_builddir)/libcmd.a: $(OBJECTS) $(LOCAL_OBJECTS)
.cc.o:
$(CXX) $(CXXFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c $< -o $@
@@ -29,4 +29,10 @@ Index: sim/ucsim/cmd.src/Makefile.in
+cmdpars.h: cmdpars.cc
cmdpars.cc: cmdpars.y
- $(YACC) -d -o $@ $<
+ $(YACC) -d $<
+ mv y.tab.c $*.cc
+- mv y.tab.h $*.hh
++ mv y.tab.h $*.h
+
+ .l.cc:
+ rm -f $@
Index: patches/patch-sim_ucsim_cmd_src_cmdlex_cc
===
RCS file: patches/patch-sim_ucsim_cmd_src_cmdlex_cc
diff -N patches/patch-sim_ucsim_cmd_src_cmdlex_cc
--- patches/patch-sim_ucsim_cmd_src_cmdlex_cc 7 Mar 2018 21:34:43 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,16 +0,0 @@
-$OpenBSD: patch-sim_ucsim_cmd_src_cmdlex_cc,v 1.1 2018/03/07 21:34:43 bcallah Exp $
-
-Allow use of in-base yacc.
-
-Index: sim/ucsim/cmd.src/cmdlex.cc
sim/ucsim/cmd.src/cmdlex.cc.orig
-+++ sim/ucsim/cmd.src/cmdlex.cc
-@@ -490,7 +490,7 @@ char *yytext;
- #include
- //#include
- #include "cmdlexcl.h"
--#include "cmdpars.hh"
-+#include "cmdpars.h"
-
- static int uc_yy_check_id(char *token);
- static int uc_yy_input(char *buf, int max_size);
Index: pkg/PLIST
===
RCS file: /cvs/ports/devel/sdcc/pkg/PLIST,v
retrieving revision 1.6
diff -u -p -r1.6 PLIST
--- pkg/PLIST 16 Apr 2018 21:09:25 - 1.6
+++ pkg/PLIST 9 Dec 2018 20:16:27 -
@@ -158,6 +158,11 @@ share/sdcc/include/mcs51/at89s8253.h
share/sdcc/include/mcs51/at89x051.h
share/sdcc/include/mcs51/at89x51.h
share/sdcc/include/mcs51/at89x52.h
+share/sdcc/include/mcs51/ax8052.h
+share/sdcc/include/mcs51/ax8052f131.h
+share/sdcc/include/mcs51/ax8052f142.h
+share/sdcc/include/mcs51/ax8052f143.h
+share/sdcc/include/mcs51/ax8052f151.h
share/sdcc/include/mcs51/cc1110.h
share/sdcc/include/mcs51/cc2430.h
share/sdcc/include/mcs51/cc2510fx.h
@@ -719,6 +724,7 @@ share/sdcc/lib/small/liblonglong.lib
share/sdcc/lib/small/libsdcc.lib
share/sdcc/lib/small/mcs51.lib
share/sdcc/lib/src/
+share/sdcc/lib/src/__assert.c
share/sdcc/lib/src/_atof.c
share/sdcc/lib/src/_autobaud.c
share/sdcc/lib/src/_bp.c
@@ -809,15 +815,16 @@ share/sdcc/lib/src/acosf.c
share/sdcc/lib/src/aligned_alloc.c
share/sdcc/lib/src/asincosf.c
share/sdcc/lib/src/asinf.c
-share/sdcc/lib/src/assert.c
share/sdcc/lib/src/atan2f.c
share/sdcc/lib/src/atanf.c
share/sdcc/lib/src/atoi.c
share/sdcc/lib/src/atol.c
share/sdcc/lib/src/atoll.c
share/sdcc/lib/src/bpx.c
+share/sdcc/lib/src/bsearch.c
share/sdcc/lib/src/btowc.c
share/sdcc/lib/src/c16rtomb.c
+share/sdcc/lib/src/c16stombs.c
share/sdcc/lib/src/c32rtomb.c
share/sdcc/lib/src/calloc.c
share/sdcc/lib/src/ceilf.c
@@ -886,6 +893,7 @@ share/sdcc/lib/src/mbrtoc16.c
share/sdcc/lib/src/mbrtoc32.c
share/sdcc/lib/src/mbrtowc.c
share/sdcc/lib/src/mbsinit.c
+share/sdcc/lib/src/mbstoc16s.c
share/sdcc/lib/src/mbstowcs.c
share/sdcc/lib/src/mbtowc.c
share/sdcc/lib/src/mcs51/
@@ -7810,6 +7818,8 @@ share/sdcc/lib/src/z80/setjmp.s
share/sdcc/lib/src/z80/strcpy.s
Re: UPDATE: x11/kde-applications/step
Nice tool, could have used this back in uni! The packaged examples work
just fine and I was able to quickly play around with particles without
fuzz.
Some things:
${WRKSRC}/TODO mentions known issues including crashes. Maybe you want
to transport this information into your package somehow so users will
know in advance (and won't bother with duplicate reports).
Please sort *_DEPENDS alphabetically.
Saw this during build, not sure if it will lead to picking up things
endusers might not have:
-- The following OPTIONAL packages have been found:
* KF5DocTools
* GSL, GSL,
Provides a GSL-powered solver for Step
* Qalculate
Also, update-plist warns about conflicts:
Warning: step-18.08.2 conflicts with kde-l10n-ar-4.14.3p4
(x11/kde4/l10n/ar):/usr/local/share/locale/ar/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-bg-4.14.3p4
(x11/kde4/l10n/bg):/usr/local/share/locale/bg/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-bs-4.14.3p4
(x11/kde4/l10n/bs):/usr/local/share/locale/bs/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-ca-4.14.3p4
(x11/kde4/l10n/ca):/usr/local/share/doc/HTML/ca/step/examples.docbook
/usr/local/share/doc/HTML/ca/step/index.cache.bz2
/usr/local/share/doc/HTML/ca/step/index.docbook
/usr/local/share/doc/HTML/ca/step/tutorials.docbook
/usr/local/share/locale/ca/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-ca@valencia-4.14.3p4
(x11/kde4/l10n/ca@valencia):/usr/local/share/locale/ca@valencia/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-cs-4.14.3p4
(x11/kde4/l10n/cs):/usr/local/share/locale/cs/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-da-4.14.3p4
(x11/kde4/l10n/da):/usr/local/share/locale/da/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-de-4.14.3p4
(x11/kde4/l10n/de):/usr/local/share/doc/HTML/de/step/examples.docbook
/usr/local/share/doc/HTML/de/step/index.cache.bz2
/usr/local/share/doc/HTML/de/step/index.docbook
/usr/local/share/doc/HTML/de/step/mainwindow.png
/usr/local/share/doc/HTML/de/step/tutorials.docbook
/usr/local/share/locale/de/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-el-4.14.3p4
(x11/kde4/l10n/el):/usr/local/share/locale/el/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-en_GB-4.14.3p4
(x11/kde4/l10n/en_GB):/usr/local/share/locale/en_GB/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-es-4.14.3p4
(x11/kde4/l10n/es):/usr/local/share/doc/HTML/es/step/examples.docbook
/usr/local/share/doc/HTML/es/step/index.cache.bz2
/usr/local/share/doc/HTML/es/step/index.docbook
/usr/local/share/doc/HTML/es/step/tutorials.docbook
/usr/local/share/locale/es/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-et-4.14.3p4
(x11/kde4/l10n/et):/usr/local/share/doc/HTML/et/step/examples.docbook
/usr/local/share/doc/HTML/et/step/index.cache.bz2
/usr/local/share/doc/HTML/et/step/index.docbook
/usr/local/share/doc/HTML/et/step/tutorials.docbook
/usr/local/share/locale/et/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-fi-4.14.3p4
(x11/kde4/l10n/fi):/usr/local/share/locale/fi/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-fr-4.14.3p4
(x11/kde4/l10n/fr):/usr/local/share/locale/fr/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-ga-4.14.3p4
(x11/kde4/l10n/ga):/usr/local/share/locale/ga/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-gl-4.14.3p4
(x11/kde4/l10n/gl):/usr/local/share/locale/gl/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-hr-4.14.3p4
(x11/kde4/l10n/hr):/usr/local/share/locale/hr/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-hu-4.14.3p4
(x11/kde4/l10n/hu):/usr/local/share/locale/hu/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-it-4.14.3p4
(x11/kde4/l10n/it):/usr/local/share/doc/HTML/it/step/examples.docbook
/usr/local/share/doc/HTML/it/step/index.cache.bz2
/usr/local/share/doc/HTML/it/step/index.docbook
/usr/local/share/doc/HTML/it/step/tutorials.docbook
/usr/local/share/locale/it/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-ja-4.14.3p4
(x11/kde4/l10n/ja):/usr/local/share/locale/ja/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-kk-4.14.3p4
(x11/kde4/l10n/kk):/usr/local/share/locale/kk/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-km-4.14.3p4
(x11/kde4/l10n/km):/usr/local/share/locale/km/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-lt-4.14.3p4
(x11/kde4/l10n/lt):/usr/local/share/locale/lt/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-lv-4.14.3p4
(x11/kde4/l10n/lv):/usr/local/share/locale/lv/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-mr-4.14.3p4
(x11/kde4/l10n/mr):/usr/local/share/locale/mr/LC_MESSAGES/step.mo
Warning: step-18.08.2 conflicts with kde-l10n-
Re: NEW: x11/kde-applications/kalzium
Works fine, nice to have this information available as offline program. Can you switch to/make it work with Python 3? I'd like to avoid unneeded dependencies on 2.7 for new ports.
Re: UPDATE archivers/fuse-zip
On Fri, Dec 07, 2018 at 09:13:27AM +0100, Klemens Nanni wrote:
> * make -> gmake symlink is needed for tests only as tests/Makefile uses
> `make' whereas Makefile already goes with proper $(MAKE) so turn
> do-configure into pre-test
> * post-install is pretty much a do-install, so simply pass the proper
> mandir and just uncompress the manual as that's the only required step
The update went without them, so I'd like to get it in now.
No package change, hence no bump.
Feedback? OK?
Index: Makefile
===
RCS file: /cvs/ports/archivers/fuse-zip/Makefile,v
retrieving revision 1.12
diff -u -p -r1.12 Makefile
--- Makefile7 Dec 2018 13:20:31 - 1.12
+++ Makefile9 Dec 2018 19:43:10 -
@@ -20,18 +20,17 @@ COMPILER = base-clang ports-gcc base-gc
LIB_DEPENDS = archivers/libzip>=0.11.2
MAKE_FLAGS = CXX="${CXX}" CXXFLAGS="${CXXFLAGS}" \
- LDFLAGS="${LDFLAGS}" prefix="${PREFIX}"
+ LDFLAGS="${LDFLAGS}"
+FAKE_FLAGS = prefix="${PREFIX}" mandir="${PREFIX}/man"
USE_GMAKE =Yes
TEST_TARGET = check
-do-configure:
- ln -s ${LOCALBASE}/bin/gmake ${WRKDIR}/bin/make
+pre-test:
+ ln -sf ${LOCALBASE}/bin/gmake ${WRKDIR}/bin/make
post-install:
- ${INSTALL_PROGRAM} ${WRKBUILD}/fuse-zip ${PREFIX}/bin
- ${INSTALL_MAN} ${WRKSRC}/fuse-zip.1 ${PREFIX}/man/man1
- rm -Rf ${PREFIX}/share/man
+ gzip -d ${PREFIX}/man/man[0-9]/*.gz
.include
[update] mpd 0.21, mpc, libmpdclient, ncmpc
Hi,
here's 4 updates for the mpd gang, libmpdclient, mpc & ncmpc are more or
less trivial, mpd was harder:
- switched from autotools to meson. I tried as hard as i could to select
the same featureset as was used with autohell.
- we cant update to 0.21.3 (latest) because ffmpeg>=57 is required since
https://github.com/MusicPlayerDaemon/MPD/commit/08272cdee2b886f759ffe632c3310e3ead095b62
- so the diff is for the latest version before this commit. I tried
updating to the latest mpd by disabling ffmpeg crap and use mpg123
instead, but it fails to link against libmpg123.
- remove the hicolor svg icon to avoid depending on gtk+3,-guic
- patches here and there to install manpages and all, disable broken
ucred detection, etc.
- in ncmpc, cast Style::FOO to int otherwise the ncurses macro complains
about it.
totally untested, will test them in the coming days. Note that mpd 0.21
requires gcc6 so it will probably give bad results on non-clang archs -
but other than that this branch has shitloads of fixes & new features
per https://raw.githubusercontent.com/MusicPlayerDaemon/MPD/v0.21/NEWS
on the other hand, we can also update to mpd 0.20.23...
testing & feedback welcome.
Landry
? mpd-0.20.20
? mpd-0.21.1
? patch-src_Main_cxx
Index: Makefile
===
RCS file: /cvs/ports/audio/mpd/Makefile,v
retrieving revision 1.117
diff -u -r1.117 Makefile
--- Makefile4 Jul 2018 09:01:59 - 1.117
+++ Makefile9 Dec 2018 21:20:26 -
@@ -2,8 +2,11 @@
BROKEN-hppa = no atomic ops
COMMENT = Music Player Daemon
-VER = 0.20.20
+# no 0.21.3, requires ffmpeg 3.1 per
+#
https://github.com/MusicPlayerDaemon/MPD/commit/08272cdee2b886f759ffe632c3310e3ead095b62
+VER = 0.21.1
DISTNAME = mpd-${VER}
+EXTRACT_SUFX = .tar.xz
CATEGORIES = audio
HOMEPAGE = https://www.musicpd.org/
MAINTAINER = David Coppa
@@ -13,11 +16,11 @@
WANTLIB = FLAC audiofile avcodec avformat avutil \
bz2 c cdio cdio_cdda cdio_paranoia curl \
- expat faad iconv icudata icui18n icuuc \
+ expat faad iconv icui18n icuuc \
id3tag iso9660 m mikmod mp3lame mpcdec \
mpdclient ogg opus pthread samplerate \
- shout sndfile sndio speex sqlite3 theora \
- vorbis vorbisenc yajl z ${COMPILER_LIBCXX}
+ shout sndfile sndio sqlite3 \
+ vorbis vorbisenc yajl ${COMPILER_LIBCXX}
MASTER_SITES = https://www.musicpd.org/download/mpd/${VER:R}/
@@ -44,69 +47,110 @@
net/libshout \
textproc/icu4c
-CONFIGURE_STYLE = gnu
-CONFIGURE_ARGS += --bindir=${PREFIX}/sbin \
- --disable-adplug \
- --disable-alsa \
- --disable-ao \
- --disable-epoll \
- --disable-fluidsynth \
- --disable-gme \
- --disable-inotify \
- --disable-jack \
- --disable-libwrap \
- --disable-mad \
- --disable-mms \
- --disable-modplug \
- --disable-mpg123 \
- --disable-nfs \
- --disable-neighbor-plugins \
- --disable-oss \
- --disable-openal \
- --disable-pulse \
- --disable-roar \
- --disable-sidplay \
- --disable-shine-encoder \
- --disable-smbclient \
- --disable-soxr \
- --disable-systemd-daemon \
- --disable-twolame-encoder \
- --disable-upnp \
- --disable-wavpack \
- --disable-wildmidi \
- --enable-aac \
- --enable-audiofile \
- --enable-bzip2 \
- --enable-cdio-paranoia \
- --enable-cue \
- --enable-curl \
- --enable-ffmpeg \
- --enable-iconv \
- --enable-lame-encoder \
- --enable-lsr \
- --enable-mikmod \
- --enable-mpc \
- --enable-opus \
- --enable-pipe-output \
- --enable-shout \
- --enable-sndfile \
- --enable-sndio \
- --enable-soundcloud \
- --enable-sqlite \
- --enable-syslog \
-
Re: UPDATE: productivity/zim-0.68
Hi,
i would like an ok to commit this.
I testes it, and it works.
/Benno
Edward Lopez-Acosta(elopezaco...@gmail.com) on 2018.12.01 19:24:42 -0600:
> Minor update, nothing depends on this, maintainer CC.
> Was able to drop one patch that no longer applied and I found no ill
> effects of doing so.
>
> Lots of bug fixes including some marked critical:
> https://github.com/jaap-karssenberg/zim-desktop-wiki/blob/master/CHANGELOG.txt
>
> Builds and runs fine on amd64.
>
> Thank you.
> --
> Edward Lopez-Acosta
> diff --git Makefile Makefile
> index cf02471b2d8..e27d5c1a241 100644
> --- Makefile
> +++ Makefile
> @@ -2,9 +2,8 @@
>
> COMMENT =desktop wiki
>
> -MODPY_EGG_VERSION = 0.67
> +MODPY_EGG_VERSION = 0.68
> DISTNAME = zim-${MODPY_EGG_VERSION}
> -REVISION = 2
>
> CATEGORIES = productivity
>
> diff --git distinfo distinfo
> index 04828b47254..221c06d9f65 100644
> --- distinfo
> +++ distinfo
> @@ -1,2 +1,2 @@
> -SHA256 (zim-0.67.tar.gz) = s3zvPUkGqiY6vMsUk5Kafqa56NEaUO2SzUN+j5P/q70=
> -SIZE (zim-0.67.tar.gz) = 2034747
> +SHA256 (zim-0.68.tar.gz) = 2RUY4BD2pulRp1MUE4tVRaTFEVH8mfUTqndooYhY3xU=
> +SIZE (zim-0.68.tar.gz) = 2044224
> diff --git patches/patch-zim_environ_py patches/patch-zim_environ_py
> deleted file mode 100644
> index b16f02c843b..000
> --- patches/patch-zim_environ_py
> +++ /dev/null
> @@ -1,14 +0,0 @@
> -$OpenBSD: patch-zim_environ_py,v 1.1 2015/05/04 19:28:16 benno Exp $
> zim/environ.py.orig Sun Apr 26 17:10:58 2015
> -+++ zim/environ.py Sun Apr 26 17:10:58 2015
> -@@ -98,8 +98,8 @@
> - if not 'APPDATA' in environ or not environ['APPDATA']:
> - environ['APPDATA'] = environ['HOME'] + '\\Application Data'
> -
> --assert isdir(environ['HOME']), \
> --'ERROR: environment variable $HOME not set correctly value is "%s"'
> -+#assert isdir(environ['HOME']), \
> -+# 'ERROR: environment variable $HOME not set correctly value is "%s"'
> - # using our own environ here to ensure encoding
> -
> - if not 'USER' in environ or not environ['USER']:
> diff --git pkg/PLIST pkg/PLIST
> index 3d783f6c74b..925766fb6ca 100644
> --- pkg/PLIST
> +++ pkg/PLIST
> @@ -273,8 +273,6 @@ lib/python${MODPY_VERSION}/site-packages/zim/www.py
> lib/python${MODPY_VERSION}/site-packages/zim/www.pyc
> @man man/man1/zim.1
> man/zim.1
> -share/appdata/
> -share/appdata/zim.appdata.xml
> share/applications/zim.desktop
> share/icons/hicolor/16x16/apps/zim.png
> share/icons/hicolor/16x16/mimetypes/application-x-zim-notebook.png
> @@ -336,6 +334,8 @@ share/locale/tr/LC_MESSAGES/zim.mo
> share/locale/uk/LC_MESSAGES/zim.mo
> share/locale/zh_CN/LC_MESSAGES/zim.mo
> share/locale/zh_TW/LC_MESSAGES/zim.mo
> +share/metainfo/
> +share/metainfo/org.zim_wiki.Zim.metainfo.xml
> share/mime/packages/zim.xml
> share/pixmaps/
> share/pixmaps/zim.png
Re: [update] devel/radare2 3.1.0
On 2018/12/09 15:43, Edd Barrett wrote: > On Sun, Dec 09, 2018 at 05:36:21AM +, David CARLIER wrote: > > Hi, > > > > there is an update for radare2 and radare2-bindings. Some functions are no longer exported in some the libraries, this requires the library major to be bumped. >From ports faq, "The rules for shared libraries are quite simple. - If functions were added to the library, you must bump the library minor number: a program that needs those functions has no way to require it except by asking explicitly for at least this version. - If the existing API changes, that is, if any function signature is altered, or if valid calling sequences are no longer valid, if a type changes in an incompatible way, the library major number must be bumped. - This includes removing old functions. Any function removal should trigger a major number bump." There is also an offset when applying patch-libr_Makefile which suggests patches haven't been updated properly. : Patching file libr/Makefile using Plan A... : Hunk #1 succeeded at 213 (offset 12 lines). : done > Looks good diff-wise, but the build fails for me. > > (I don't have the old version installed) > > I'm running: > OpenBSD 6.4-current (GENERIC.MP) #493: Wed Dec 5 22:00:48 MST 2018 It does build ok for me on amd64 here. (It's one of those annoying ports that fails if the old version is installed but that's a different error). Full working build log at https://junkpile.org/radare2-3.1.0.log if you want to diff and see if anything becomes apparent .. > ---8<--- > ... > gmake -C binr > gmake[1]: Entering directory > '/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/binr' > gmake[2]: Entering directory > '/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/binr/rax2' > cc -c -O2 -pipe -O2 -pipe -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 > -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -O2 -pipe -MD -fPIC -g > -Wall -D__UNIX__=1 > -I/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/libr/..//libr/include -o > rax2.o rax2.c > cc -O2 -pipe -O2 -pipe -O2 -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -O2 > -pipe -MD -fPIC -g -Wall -D__UNIX__=1 -O2 -pipe -MD -fPIC -g -Wall > -D__UNIX__=1 > -I/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/libr/..//libr/include > rax2.o -L.. -o rax2 -L/usr/local/lib -lpthread -lm > -L/usr/local/pobj/radare2-3.1.0/radare2-3.1.0/libr/util -lr_util -fPIC > -lz -lzip > /usr/bin/ld: error: undefined symbol: ret_ascii_table > >>> referenced by rax2.c:75 > >>> rax2.o:(rax) > > /usr/bin/ld: error: undefined symbol: r_hex_from_code > >>> referenced by rax2.c:391 > >>> rax2.o:(rax) > > /usr/bin/ld: error: undefined symbol: r_print_hex_from_bin > >>> referenced by rax2.c:469 > >>> rax2.o:(rax) > cc: error: linker command failed with exit code 1 (use -v to see > invocation) > --->8--- > > -- > Best Regards > Edd Barrett > > http://www.theunixzoo.co.uk >
mpv: small assorted port changes
After aja@ committed my DO_WAF bits from the bigger update diff, here
are the other changes I'd like to get in unrelated to the new version:
* use TLS
* use Python 3
* use SEPARATE_BUILD
- dropping the manual WRKBUILD actually moves it outside WRKSRC
Builds, packages and runs fine on amd64.
Haven't heard from MAINTAINER since a long time.
Feedback? OK?
Index: Makefile
===
RCS file: /cvs/ports/multimedia/mpv/Makefile,v
retrieving revision 1.44
diff -u -p -r1.44 Makefile
--- Makefile25 Nov 2018 10:09:25 - 1.44
+++ Makefile9 Dec 2018 23:06:20 -
@@ -5,16 +5,16 @@ COMMENT = movie player based on MPlayer
GH_ACCOUNT = mpv-player
GH_PROJECT = mpv
GH_TAGNAME = v0.22.0
-REVISION = 5
+REVISION = 6
CATEGORIES = multimedia x11
-HOMEPAGE = http://mpv.io/
+HOMEPAGE = https://mpv.io/
MAINTAINER = Dmitrij D. Czarkoff
WAF = ${WRKSRC}/waf-1.8.19
-MASTER_SITES0 =http://waf.io/
+MASTER_SITES0 =https://waf.io/
DISTFILES =${DISTNAME}{${GH_TAGNAME}}${EXTRACT_SUFX} ${WAF:T}:0
EXTRACT_ONLY = ${DISTNAME}${EXTRACT_SUFX}
@@ -33,6 +33,8 @@ WANTLIB += xcb-glx z ${MODLUA_WANTLIB}
MODULES = lang/lua \
lang/python
+MODPY_RUNDEP = No
+MODPY_VERSION =${MODPY_DEFAULT_VERSION_3}
BUILD_DEPENDS =audio/ladspa \
textproc/py-docutils
@@ -49,10 +51,10 @@ LIB_DEPENDS = audio/libcdio \
multimedia/libdvdnav \
multimedia/libv4l
-MODPY_RUNDEP = No
RUN_DEPENDS = devel/desktop-file-utils \
x11/gtk+3,-guic
+SEPARATE_BUILD = Yes
CONFIGURE_ARGS = --confloaddir=${SYSCONFDIR}/mpv \
--confdir=${LOCALBASE}/share/examples/mpv \
--mandir=${LOCALBASE}/man \
@@ -95,8 +97,6 @@ MAKE_ENV += CPPFLAGS="-I${LOCALBASE}/in
MAKE_FLAGS = -o "${WRKBUILD}" -t "${WRKSRC}" --destdir="${DESTDIR}"
NO_TEST = Yes
-
-WRKBUILD = ${WRKSRC}/${MACHINE_ARCH}
.if ${MACHINE_ARCH} == "i386"
CFLAGS += -march=i586
UPDATE: textproc/py-sphinx_rtd_theme-0.4.2
Update to current version.
Lots of bug fixes, and the only consumer is py-sphinx. I tested a few
site builds using sphinx with this and found no issues using the sphinx
version currently in the tree.
Builds, installs and runs fine on amd64.
Deps checked, MAINTAINER CC'ed, and no tests defined since its a
collection of CSS, HTML, and JS files.
Comments/feedback?
--
Edward Lopez-Acosta
diff --git Makefile Makefile
index f51ba453d95..909ecb1b1fa 100644
--- Makefile
+++ Makefile
@@ -2,7 +2,7 @@
COMMENT = readthedocs.org theme for Sphinx
-MODPY_EGG_VERSION = 0.2.4
+MODPY_EGG_VERSION = 0.4.2
DISTNAME = sphinx_rtd_theme-${MODPY_EGG_VERSION}
PKGNAME = py-${DISTNAME}
diff --git distinfo distinfo
index 9c37ef56472..90905d2fb3c 100644
--- distinfo
+++ distinfo
@@ -1,2 +1,2 @@
-SHA256 (sphinx_rtd_theme-0.2.4.tar.gz) = LfdLj/b65pZcUn6XzKbGyUSIaq5HS0kOF/kq376ENBc=
-SIZE (sphinx_rtd_theme-0.2.4.tar.gz) = 1392456
+SHA256 (sphinx_rtd_theme-0.4.2.tar.gz) = AvAqZ21rqrt1iiDHpHnVhkjg9k8T4H0bOI6bsq/oagk=
+SIZE (sphinx_rtd_theme-0.4.2.tar.gz) = 5388206
diff --git pkg/PLIST pkg/PLIST
index 5a74789d94f..475d85e507f 100644
--- pkg/PLIST
+++ pkg/PLIST
@@ -4,7 +4,9 @@ lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme-${MODPY_EGG_VERSION}-p
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/PKG-INFO
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/SOURCES.txt
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/dependency_links.txt
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/entry_points.txt
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/not-zip-safe
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/requires.txt
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme-${MODPY_EGG_VERSION}-py${MODPY_VERSION}.egg-info/top_level.txt
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/__init__.py
${MODPY_COMMENT}lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/${MODPY_PYCACHE}/
@@ -12,7 +14,6 @@ lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/${MODPY_PYCACHE}__init
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/breadcrumbs.html
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/footer.html
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/layout.html
-lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/layout_old.html
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/search.html
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/searchbox.html
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/
@@ -20,16 +21,37 @@ lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/css/
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/css/badge_only.css
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/css/theme.css
lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/
-lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Inconsolata-Bold.ttf
-lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Inconsolata-Regular.ttf
-lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato-Bold.ttf
-lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato-Regular.ttf
-lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/RobotoSlab-Bold.ttf
-lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/RobotoSlab-Regular.ttf
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-bold.eot
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-bold.ttf
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-bold.woff
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-bold.woff2
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-bolditalic.eot
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-bolditalic.ttf
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-bolditalic.woff
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-bolditalic.woff2
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-italic.eot
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-italic.ttf
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-italic.woff
+lib/python${MODPY_VERSION}/site-packages/sphinx_rtd_theme/static/fonts/Lato/lato-italic.woff2
+lib/python${MODPY_VERSIO
Re: UPDATE: www/py-flask-login-0.4.1 + add py3 flavor
On Mon, 03 Dec 2018 at 18:59:17 -0600, Edward Lopez-Acosta wrote: > Version update due to being quite out of date. Also added a py3 flavor since > it was not present. > > Built fine for both py2 and py3 and has no tests. > > $ sqlite3 /usr/local/share/sqlports "select * from depends where dependspath > like 'www/py-flask-login' or dependspath like 'www/py-flask-login,python3'" > | wc -l >0 > > Thoughts? > Thank you, > -- > Edward Lopez-Acosta OK abieber@ if anoyne wants to commit! -- PGP: 0x1F81112D62A9ADCE / 3586 3350 BFEA C101 DB1A 4AF0 1F81 112D 62A9 ADCE
UPDATE: devel/p5-Modern-Perl
Hi, This update includes support of Perl 5.26 & 5.28. It's tested on amd64 current. Tests & comments welcome. OK? Index: Makefile === RCS file: /cvs/ports/devel/p5-Modern-Perl/Makefile,v retrieving revision 1.4 diff -u -p -r1.4 Makefile --- Makefile24 Mar 2017 15:56:38 - 1.4 +++ Makefile7 Dec 2018 09:00:05 - @@ -5,7 +5,7 @@ COMMENT = enable all of the features of MODULES = cpan PKG_ARCH = * CPAN_AUTHOR = CHROMATIC -DISTNAME = Modern-Perl-1.20170117 +DISTNAME = Modern-Perl-1.20181021 CATEGORIES = devel MAINTAINER = Edward Index: distinfo === RCS file: /cvs/ports/devel/p5-Modern-Perl/distinfo,v retrieving revision 1.3 diff -u -p -r1.3 distinfo --- distinfo24 Mar 2017 15:56:38 - 1.3 +++ distinfo7 Dec 2018 09:00:05 - @@ -1,2 +1,2 @@ -SHA256 (Modern-Perl-1.20170117.tar.gz) = XfKoNGEWMhLbIrnDNTYGoaEjYWgg/lBnUEHDTwBLNig= -SIZE (Modern-Perl-1.20170117.tar.gz) = 13867 +SHA256 (Modern-Perl-1.20181021.tar.gz) = HUgrUo98bGD4aNfQvw/MnDZoJQ3ET8s5qVt8Y+CSycU= +SIZE (Modern-Perl-1.20181021.tar.gz) = 14234
UPDATE: devel/py-whichcraft-0.5.2
Update to latest version.
Changes include python3.7 compatibility and cleaned up code formatting.
Temporary patch included for invalid characters in the README.rst. Issue
already noted upstream.
https://github.com/pydanny/whichcraft/issues/10
- No MAINTAINER listed
- All tests pass for py2 and py3
- Nothing depends on this
- diff applies cleanly with `patch`
Comments/feedback?
Thank you,
--
Edward Lopez-Acosta
diff --git Makefile Makefile
index 365fed99eb6..88603781fd0 100644
--- Makefile
+++ Makefile
@@ -2,7 +2,7 @@
COMMENT = cross-platform, cross-python, shutil.which functionality
-MODPY_EGG_VERSION = 0.4.1
+MODPY_EGG_VERSION = 0.5.2
DISTNAME = whichcraft-${MODPY_EGG_VERSION}
PKGNAME = py-whichcraft-${MODPY_EGG_VERSION}
diff --git distinfo distinfo
index 0e0cd843a20..ff78384225a 100644
--- distinfo
+++ distinfo
@@ -1,2 +1,2 @@
-SHA256 (whichcraft-0.4.1.tar.gz) = ng1RyTh8t+nyi37bVJ5qA9p1j3eE+ZHrQ5fX94CMV/0=
-SIZE (whichcraft-0.4.1.tar.gz) = 6222
+SHA256 (whichcraft-0.5.2.tar.gz) = /s3dUx8jf/xduLIVQJr7GPowMAaZBkzKSBdSG0/IGBU=
+SIZE (whichcraft-0.5.2.tar.gz) = 6480
diff --git patches/patch-README_rst patches/patch-README_rst
new file mode 100644
index 000..e97299f342f
--- /dev/null
+++ patches/patch-README_rst
@@ -0,0 +1,16 @@
+$OpenBSD$
+
+Index: README.rst
+--- README.rst.orig
README.rst
+@@ -34,8 +34,8 @@ On Linux, Mac, Windows for Python 2.7 or any of the ma
+
+ .. code-block:: python
+
+- Â >>> from whichcraft import which
+- Â >>> which('date')
++>>> from whichcraft import which
++>>> which('date')
+ '/bin/date'
+ >>> which('calendar')
+ '/bin/calendar'
tiny bsd.pork.mk error?
having updated ports tree to rebuild mercurial, i noticed this error. ===> Looking for mercurial-x11-4.5.3p3.tgz in $PKG_PATH - not found *** Error 1 in . (/home/tedu/ports/infrastructure/mk/bsd.port.mk:1992 '/home/tedu/ports/packages/sparc64/c ache/mercurial-x11-4.5.3p3.tgz': @...) Everything built and installed correctly, otherwise. Perhaps operator error, I am not sure if the command actually failed, FETCH_PACKAGES=Yes seemed to work for other packages. This is 6.4. Looking at line 1992 didn't reveal much.
[UPDATE] mail/ruby-mime-types =>3.2.2
Update to 3.2.2 from 3.1 attached
Index: Makefile
===
RCS file: /cvs/ports/mail/ruby-mime-types/Makefile,v
retrieving revision 1.13
diff -u -p -r1.13 Makefile
--- Makefile 2 Nov 2016 19:31:33 - 1.13
+++ Makefile 10 Dec 2018 03:31:50 -
@@ -2,7 +2,7 @@
COMMENT= MIME type library for Ruby
-DISTNAME= mime-types-3.1
+DISTNAME= mime-types-3.2.2
CATEGORIES= mail
HOMEPAGE= https://github.com/mime-types/ruby-mime-types/
Index: distinfo
===
RCS file: /cvs/ports/mail/ruby-mime-types/distinfo,v
retrieving revision 1.5
diff -u -p -r1.5 distinfo
--- distinfo 2 Nov 2016 19:31:33 - 1.5
+++ distinfo 10 Dec 2018 03:31:50 -
@@ -1,2 +1,2 @@
-SHA256 (mime-types-3.1.gem) = dZSTIcP1XmYY0FlgFgWYQcJhaDQuwe5OZBBTu2b6BwE=
-SIZE (mime-types-3.1.gem) = 42496
+SHA256 (mime-types-3.2.2.gem) = k/MI8LZ1SwylDdGYK4F/ZbiUb2o0vT22vT2KUmXwXTo=
+SIZE (mime-types-3.2.2.gem) = 35840
Index: pkg/DESCR
===
RCS file: /cvs/ports/mail/ruby-mime-types/pkg/DESCR,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 DESCR
--- pkg/DESCR 19 Apr 2008 18:00:45 - 1.1.1.1
+++ pkg/DESCR 10 Dec 2018 03:31:50 -
@@ -1,3 +1,3 @@
-This library allows for the identification of a file's likely MIME content
-type. The identification of MIME content type is based on a file's filename
-extensions.
+This library allows for the identification of a file's likely MIME
+content type. The identification of MIME content type is based on
+a file's filename extensions.
Index: pkg/PLIST
===
RCS file: /cvs/ports/mail/ruby-mime-types/pkg/PLIST,v
retrieving revision 1.4
diff -u -p -r1.4 PLIST
--- pkg/PLIST 2 Nov 2016 19:31:33 - 1.4
+++ pkg/PLIST 10 Dec 2018 03:31:50 -
@@ -1,10 +1,10 @@
@comment $OpenBSD: PLIST,v 1.4 2016/11/02 19:31:33 jeremy Exp $
${GEM_LIB}/cache/${DISTNAME}.gem
${GEM_LIB}/gems/${DISTNAME}/
-${GEM_LIB}/gems/${DISTNAME}/Code-of-Conduct.rdoc
-${GEM_LIB}/gems/${DISTNAME}/Contributing.rdoc
-${GEM_LIB}/gems/${DISTNAME}/History.rdoc
-${GEM_LIB}/gems/${DISTNAME}/Licence.rdoc
+${GEM_LIB}/gems/${DISTNAME}/Code-of-Conduct.md
+${GEM_LIB}/gems/${DISTNAME}/Contributing.md
+${GEM_LIB}/gems/${DISTNAME}/History.md
+${GEM_LIB}/gems/${DISTNAME}/Licence.md
${GEM_LIB}/gems/${DISTNAME}/Manifest.txt
${GEM_LIB}/gems/${DISTNAME}/README.rdoc
${GEM_LIB}/gems/${DISTNAME}/Rakefile
[UPDATE] mail/ruby-mime-types-data
update to 3.2018.0812.
Index: Makefile
===
RCS file: /cvs/ports/mail/ruby-mime-types-data/Makefile,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 Makefile
--- Makefile 2 Nov 2016 19:29:32 - 1.1.1.1
+++ Makefile 10 Dec 2018 03:46:14 -
@@ -2,7 +2,7 @@
COMMENT= MIME types data for Ruby
-DISTNAME= mime-types-data-3.2016.0521
+DISTNAME= mime-types-data-3.2018.0812
CATEGORIES= mail
HOMEPAGE= https://github.com/mime-types/mime-types-data/
Index: distinfo
===
RCS file: /cvs/ports/mail/ruby-mime-types-data/distinfo,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 distinfo
--- distinfo 2 Nov 2016 19:29:32 - 1.1.1.1
+++ distinfo 10 Dec 2018 03:46:14 -
@@ -1,2 +1,2 @@
-SHA256 (mime-types-data-3.2016.0521.gem) = dUK8z/BtcMStlNHPELfaxr2JlYNW5dDX9kRxaMgZvhI=
-SIZE (mime-types-data-3.2016.0521.gem) = 101888
+SHA256 (mime-types-data-3.2018.0812.gem) = rEVTKIIldWlw8HOXmP8PERaYjVbgrBWlJVU+wRW4mx8=
+SIZE (mime-types-data-3.2018.0812.gem) = 157184
Index: pkg/DESCR
===
RCS file: /cvs/ports/mail/ruby-mime-types-data/pkg/DESCR,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 DESCR
--- pkg/DESCR 2 Nov 2016 19:29:32 - 1.1.1.1
+++ pkg/DESCR 10 Dec 2018 03:46:14 -
@@ -1,4 +1,5 @@
-mime-types-data provides a registry for information about MIME media type
-definitions. It can be used with the Ruby mime-types library or other software
-to determine defined filename extensions for MIME types, or to use filename
-extensions to look up the likely MIME type definitions.
+mime-types-data provides a registry for information about MIME media
+type definitions. It can be used with the Ruby mime-types library
+or other software to determine defined filename extensions for MIME
+types, or to use filename extensions to look up the likely MIME
+type definitions.
Index: pkg/PLIST
===
RCS file: /cvs/ports/mail/ruby-mime-types-data/pkg/PLIST,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 PLIST
--- pkg/PLIST 2 Nov 2016 19:29:32 - 1.1.1.1
+++ pkg/PLIST 10 Dec 2018 03:46:14 -
@@ -23,4 +23,18 @@ ${GEM_LIB}/gems/${DISTNAME}/lib/mime/
${GEM_LIB}/gems/${DISTNAME}/lib/mime-types-data.rb
${GEM_LIB}/gems/${DISTNAME}/lib/mime/types/
${GEM_LIB}/gems/${DISTNAME}/lib/mime/types/data.rb
+${GEM_LIB}/gems/${DISTNAME}/types/
+${GEM_LIB}/gems/${DISTNAME}/types/application.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/audio.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/chemical.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/conference.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/drawing.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/font.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/image.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/message.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/model.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/multipart.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/text.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/video.yaml
+${GEM_LIB}/gems/${DISTNAME}/types/world.yaml
${GEM_LIB}/specifications/${DISTNAME}.gemspec
LLVM 6.0.1p8 fails to compile on 6.4-stable/loongson
Hi, As title says. LLVM 6.0.1p8 build fails due to missing header files. The most relevant outputs: #+BEGIN_QUOTE In file included from /usr/ports/pobj/llvm-6.0.1/llvm-6.0.1.src/tools/lldb/source/Interpreter/CommandInterpreter.cpp:53:0: /usr/ports/pobj/llvm-6.0.1/llvm-6.0.1.src/tools/lldb/include/lldb/Host/Editline.h:49:19: fatal error: codecvt: No such file or directory #include ^ compilation terminated. ninja: build stopped: subcommand failed. #+END_QUOTE The full build log is also attached. Please advice on how to fix or debug. Thanks. -- manphiz llvm,,-main.log.gz Description: application/gzip signature.asc Description: PGP signature
Re: LLVM 6.0.1p8 fails to compile on 6.4-stable/loongson
On 12/9/18 10:49 PM, Xiyue Deng wrote: Hi, As title says. LLVM 6.0.1p8 build fails due to missing header files. The most relevant outputs: #+BEGIN_QUOTE In file included from /usr/ports/pobj/llvm-6.0.1/llvm-6.0.1.src/tools/lldb/source/Interpreter/CommandInterpreter.cpp:53:0: /usr/ports/pobj/llvm-6.0.1/llvm-6.0.1.src/tools/lldb/include/lldb/Host/Editline.h:49:19: fatal error: codecvt: No such file or directory #include ^ compilation terminated. ninja: build stopped: subcommand failed. #+END_QUOTE The full build log is also attached. Please advice on how to fix or debug. Thanks. https://marc.info/?l=openbsd-ports&m=154325649707215&w=2
Re: LLVM 6.0.1p8 fails to compile on 6.4-stable/loongson
Brian Callahan writes: > On 12/9/18 10:49 PM, Xiyue Deng wrote: >> Hi, >> >> As title says. LLVM 6.0.1p8 build fails due to missing header files. >> The most relevant outputs: >> >> #+BEGIN_QUOTE >> In file included from >> /usr/ports/pobj/llvm-6.0.1/llvm-6.0.1.src/tools/lldb/source/Interpreter/CommandInterpreter.cpp:53:0: >> /usr/ports/pobj/llvm-6.0.1/llvm-6.0.1.src/tools/lldb/include/lldb/Host/Editline.h:49:19: >> fatal error: codecvt: No such file or directory >> #include >> ^ >> compilation terminated. >> ninja: build stopped: subcommand failed. >> #+END_QUOTE >> >> The full build log is also attached. Please advice on how to fix or debug. >> >> Thanks. >> > > https://marc.info/?l=openbsd-ports&m=154325649707215&w=2 Thanks. It will be great that the same patch can be applied to mips64* as well. -- manphiz
Re: Update vmm-firmware port
On Sun, Dec 09, 2018 at 12:19:46PM +0100, Claudio Jeker wrote:
> I started looking at supporting fw_cfg in vmd. Now to make this work with
> SeaBIOS there are a few fixes needed. First of all the way it reads the
> FW_CFG_DATA port is not supported by vmm(4) (problem whith 'rep insb' on
> IO ports). Additionally this cleans up some of the patches which I think
> are not needed if the setting of screen-and-debug is changed. At least I
> no longer see double printing of messages.
> I enabled CONFIG_BOOTORDER because this is what I would like to tweak.
> The CONFIG_DEBUG_LEVEL can be taken out before commit but it helped me
> debugging this. Once vmd uses fw_cfg more of the patches can be removed.
>
> --
> :wq Claudio
>
While I am not opposed to vmm-firmware updates in general, we have to be
careful a bit now since there are tons of people using all sorts of bizarre
linux distributions, which all do different things with the bios during boot.
I'd think we would need to put this out there for a long while before I'd
feel comfortable turning it on for everyone.
I did not read the diff yet but I will.
-ml
> Index: Makefile
> ===
> RCS file: /cvs/ports/sysutils/firmware/vmm/Makefile,v
> retrieving revision 1.15
> diff -u -p -r1.15 Makefile
> --- Makefile 21 Nov 2018 00:26:05 - 1.15
> +++ Makefile 9 Dec 2018 11:09:05 -
> @@ -13,7 +13,7 @@ CC =/usr/bin/gcc
> FW_DRIVER= vmm
> FW_VER= 1.11.0
> SB_VER= 20100422
> -REVISION=0
> +REVISION=1
> DISTNAME=seabios-${FW_VER}
> DISTFILES= ${DISTNAME}${EXTRACT_SUFX} \
> sgabios-20100422{23d474943dcd55d0550a3d20b3d30e9040a4f15b}.tar.gz:0
> Index: files/config
> ===
> RCS file: /cvs/ports/sysutils/firmware/vmm/files/config,v
> retrieving revision 1.6
> diff -u -p -r1.6 config
> --- files/config 11 Jul 2018 09:09:46 - 1.6
> +++ files/config 7 Dec 2018 20:34:05 -
> @@ -15,7 +15,7 @@ CONFIG_QEMU_HARDWARE=y
> # CONFIG_THREADS is not set
> # CONFIG_RELOCATE_INIT is not set
> # CONFIG_BOOTMENU is not set
> -# CONFIG_BOOTORDER is not set
> +CONFIG_BOOTORDER=y
> # CONFIG_ENTRY_EXTRASTACK is not set
> CONFIG_MALLOC_UPPERMEMORY=y
> CONFIG_ROM_SIZE=0
> @@ -92,7 +92,7 @@ CONFIG_VGA_EXTRA_STACK_SIZE=512
> #
> # Debugging
> #
> -CONFIG_DEBUG_LEVEL=-1
> +CONFIG_DEBUG_LEVEL=1
> CONFIG_DEBUG_SERIAL=y
> CONFIG_DEBUG_SERIAL_PORT=0x3f8
> CONFIG_DEBUG_IO=n
> Index: patches/patch-src_boot_c
> ===
> RCS file: patches/patch-src_boot_c
> diff -N patches/patch-src_boot_c
> --- patches/patch-src_boot_c 11 Jul 2018 09:09:46 - 1.1
> +++ /dev/null 1 Jan 1970 00:00:00 -
> @@ -1,43 +0,0 @@
> src/boot.c.orig Tue Jul 10 14:52:11 2018
> -+++ src/boot.c Tue Jul 10 14:53:18 2018
> -@@ -659,7 +659,7 @@ boot_cdrom(struct drive_s *drive)
> - {
> - if (! CONFIG_CDROM_BOOT)
> - return;
> --printf("Booting from DVD/CD...\n");
> -+dprintf(1, "Booting from DVD/CD...\n");
> -
> - int status = cdrom_boot(drive);
> - if (status) {
> -@@ -685,7 +685,7 @@ boot_cbfs(struct cbfs_file *file)
> - {
> - if (!CONFIG_COREBOOT_FLASH)
> - return;
> --printf("Booting from CBFS...\n");
> -+dprintf(1, "Booting from CBFS...\n");
> - cbfs_run_payload(file);
> - }
> -
> -@@ -693,7 +693,7 @@ boot_cbfs(struct cbfs_file *file)
> - static void
> - boot_rom(u32 vector)
> - {
> --printf("Booting from ROM...\n");
> -+dprintf(1, "Booting from ROM...\n");
> - struct segoff_s so;
> - so.segoff = vector;
> - call_boot_entry(so, 0);
> -@@ -733,11 +733,11 @@ do_boot(int seq_nr)
> - struct bev_s *ie = &BEV[seq_nr];
> - switch (ie->type) {
> - case IPL_TYPE_FLOPPY:
> --printf("Booting from Floppy...\n");
> -+dprintf(1, "Booting from Floppy...\n");
> - boot_disk(0x00, CheckFloppySig);
> - break;
> - case IPL_TYPE_HARDDISK:
> --printf("Booting from Hard Disk...\n");
> -+dprintf(1, "Booting from Hard Disk...\n");
> - boot_disk(0x80, 1);
> - break;
> - case IPL_TYPE_CDROM:
> Index: patches/patch-src_fw_paravirt_c
> ===
> RCS file: /cvs/ports/sysutils/firmware/vmm/patches/patch-src_fw_paravirt_c,v
> retrieving revision 1.2
> diff -u -p -r1.2 patch-src_fw_paravirt_c
> --- patches/patch-src_fw_paravirt_c 26 Apr 2018 12:23:32 - 1.2
> +++ patches/patch-src_fw_paravirt_c 9 Dec 2018 10:55:37 -
> @@ -1,18 +1,27 @@
> $OpenBSD: patch-src_fw_paravirt_c,v 1.2 2018/04/26 12:23:32 sthen Exp $
>
> +Don't use 'rep insb' to read IO ports, vmm does not support that yet.
> Allow detection of >4GB RAM. Normally seabios only allows this with the
> qemu config device which VMM doesn't have.
>
> Index:
Re: LLVM 6.0.1p8 fails to compile on 6.4-stable/loongson
On Sun, Dec 09, 2018 at 09:31:14PM -0800, Xiyue Deng wrote: > > Brian Callahan writes: > > > On 12/9/18 10:49 PM, Xiyue Deng wrote: > >> Hi, > >> > >> As title says. LLVM 6.0.1p8 build fails due to missing header files. > >> The most relevant outputs: > >> > >> #+BEGIN_QUOTE > >> In file included from > >> /usr/ports/pobj/llvm-6.0.1/llvm-6.0.1.src/tools/lldb/source/Interpreter/CommandInterpreter.cpp:53:0: > >> /usr/ports/pobj/llvm-6.0.1/llvm-6.0.1.src/tools/lldb/include/lldb/Host/Editline.h:49:19: > >> fatal error: codecvt: No such file or directory > >> #include > >> ^ > >> compilation terminated. > >> ninja: build stopped: subcommand failed. > >> #+END_QUOTE > >> > >> The full build log is also attached. Please advice on how to fix or debug. > >> > >> Thanks. > >> > > > > https://marc.info/?l=openbsd-ports&m=154325649707215&w=2 > > Thanks. It will be great that the same patch can be applied to mips64* > as well. What was finally commited is https://marc.info/?l=openbsd-ports-cvs&m=154413306823025&w=2, which takes care of knocking out the lldb subpackage on GCC4_ARCHS. On -current, the ports *should* build now. Landry
Re: boost diff
On Sat Dec 08, 2018 at 09:11:10PM +, Stuart Henderson wrote: > +cc boost co-maintainers > > On 2018/12/04 11:34, Otto Moerbeek wrote: > > On Sat, Dec 01, 2018 at 08:16:33PM +0100, Otto Moerbeek wrote: > > > > > On Fri, Nov 30, 2018 at 01:06:18PM +, Stuart Henderson wrote: > > > > > > > On 2018/11/30 13:53, Otto Moerbeek wrote: > > > > > No luck on i386 so far. sp;arc64 ios also not going to work, since the > > > > > boost context lib has no sparc64 support at al. In the meantime I'm > > > > > building arm boost, but that takes ages, it;s now building the > > > > > gcc-4.9.4 port needed by some boost dependency... > > > > > > > > > > Can the impact analysis be done on amd64? > > > > > > > > It can, but not by me, the only bulk building environment I have is > > > > i386. > > > > If there's someone who can do a test bulk build with the diff and run > > > > this under script(1) and send me the output (there will be a lot as we > > > > haven't done a WANTLIB sync for ages) I'll look over it .. > > > > > > > > cd /usr/ports/packages/amd64/all > > > > /usr/ports/infrastructure/bin/check-lib-depends -d . -q -x ./* > > > > > > > > > > Ib the meantime I built patched boost on arm, and tests work out fine > > > (including pdns_recusror). > > > > > > -Otto > > > > > > > The status so far: > > > > amd64: boost context is working fine > > > > i386: only working with a very simple test program, anything using fp > > crashes > > > > arm:working fine. > > > > aarch64: after getting boost to build by skipping the numpy dependency > > (which does not build since there is no gcc 4.9 which is > > required to build fortran dependencies) it also works. > > > > So all in all I think boost context can be enabled for amd64 and arm > > at this moment, provided it does not break anything else. For that I > > need the report sthen@ described above. Any takers? > > > > If the above report looks good I'll submit a full diff, converting all stack > > allocaters to use the proper mmap flag and enabling context only for > > amd64 and arm. We can look at aarch64 and i386 later. > > > > -Otto > > > > Thanks to core developer ajacoutot@ ;) for the bulk build which is > looking good (no failures, nothing unintended picking up the new > libraries in a check-lib-depends run). > > Here's a modified version of Otto's diff. Rather than using PFRAG. > files I've adjusted it to split the new libraries off to a subpackage > built only on the relevant architectures; this needs REVISION bumps in > dependent ports (which I can handle), that way ports requiring these > libraries (e.g. powerdns recursor when ready) can just depend on the > subpackage, and keep the machine-dependent parts in one place (boost). > > Any comments? Does this seem like the right approach? We could use > selective included PFRAG files and a single package instead but as I see > it the only advantage is not having to bump dep's. > > > :| OK, so here's my diffs to be processed further. It contains the i386 > :| assembly stuff, the stack allocation changes and also a diff to the b2 > :| build process to make it not consume 100% cpu. That's an ugly diff, > :| but I didn't find the actual cause of the zero timeout to the poll() > :| call yet. > > (The latter-mentioned diff is the select_timeout patch.) > > I'm fine with a subpackage I guess that approach is much more bulk-build friendly but this decision is up to the bulk-core-team. Anyway, thank you very much for working on this topic. If bulk is green ok rsadowski@ Rafael Sadowski
Re: UPDATE: x11/kde-applications/step
On Sun Dec 09, 2018 at 09:38:05PM +0100, Klemens Nanni wrote:
> Nice tool, could have used this back in uni! The packaged examples work
> just fine and I was able to quickly play around with particles without
> fuzz.
>
> Some things:
>
> ${WRKSRC}/TODO mentions known issues including crashes. Maybe you want
> to transport this information into your package somehow so users will
> know in advance (and won't bother with duplicate reports).
The bug-report is from 2014. I don't bother about that.
>
> Please sort *_DEPENDS alphabetically.
ACK; I added a new ordered completed list
>
> Saw this during build, not sure if it will lead to picking up things
> endusers might not have:
>
> -- The following OPTIONAL packages have been found:
>
> * KF5DocTools
> * GSL, GSL,
> Provides a GSL-powered solver for Step
> * Qalculate
It's in the LIB_DEPENDS.
>
>
> Also, update-plist warns about conflicts:
Yes but tags are in. You will see this conflicts for almost all KDE5
packages and of course you find the conflict tags in PLIST.
>
> Warning: step-18.08.2 conflicts with kde-l10n-ar-4.14.3p4
> (x11/kde4/l10n/ar):/usr/local/share/locale/ar/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-bg-4.14.3p4
> (x11/kde4/l10n/bg):/usr/local/share/locale/bg/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-bs-4.14.3p4
> (x11/kde4/l10n/bs):/usr/local/share/locale/bs/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-ca-4.14.3p4
> (x11/kde4/l10n/ca):/usr/local/share/doc/HTML/ca/step/examples.docbook
> /usr/local/share/doc/HTML/ca/step/index.cache.bz2
> /usr/local/share/doc/HTML/ca/step/index.docbook
> /usr/local/share/doc/HTML/ca/step/tutorials.docbook
> /usr/local/share/locale/ca/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-ca@valencia-4.14.3p4
> (x11/kde4/l10n/ca@valencia):/usr/local/share/locale/ca@valencia/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-cs-4.14.3p4
> (x11/kde4/l10n/cs):/usr/local/share/locale/cs/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-da-4.14.3p4
> (x11/kde4/l10n/da):/usr/local/share/locale/da/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-de-4.14.3p4
> (x11/kde4/l10n/de):/usr/local/share/doc/HTML/de/step/examples.docbook
> /usr/local/share/doc/HTML/de/step/index.cache.bz2
> /usr/local/share/doc/HTML/de/step/index.docbook
> /usr/local/share/doc/HTML/de/step/mainwindow.png
> /usr/local/share/doc/HTML/de/step/tutorials.docbook
> /usr/local/share/locale/de/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-el-4.14.3p4
> (x11/kde4/l10n/el):/usr/local/share/locale/el/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-en_GB-4.14.3p4
> (x11/kde4/l10n/en_GB):/usr/local/share/locale/en_GB/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-es-4.14.3p4
> (x11/kde4/l10n/es):/usr/local/share/doc/HTML/es/step/examples.docbook
> /usr/local/share/doc/HTML/es/step/index.cache.bz2
> /usr/local/share/doc/HTML/es/step/index.docbook
> /usr/local/share/doc/HTML/es/step/tutorials.docbook
> /usr/local/share/locale/es/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-et-4.14.3p4
> (x11/kde4/l10n/et):/usr/local/share/doc/HTML/et/step/examples.docbook
> /usr/local/share/doc/HTML/et/step/index.cache.bz2
> /usr/local/share/doc/HTML/et/step/index.docbook
> /usr/local/share/doc/HTML/et/step/tutorials.docbook
> /usr/local/share/locale/et/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-fi-4.14.3p4
> (x11/kde4/l10n/fi):/usr/local/share/locale/fi/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-fr-4.14.3p4
> (x11/kde4/l10n/fr):/usr/local/share/locale/fr/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-ga-4.14.3p4
> (x11/kde4/l10n/ga):/usr/local/share/locale/ga/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-gl-4.14.3p4
> (x11/kde4/l10n/gl):/usr/local/share/locale/gl/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-hr-4.14.3p4
> (x11/kde4/l10n/hr):/usr/local/share/locale/hr/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-hu-4.14.3p4
> (x11/kde4/l10n/hu):/usr/local/share/locale/hu/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-it-4.14.3p4
> (x11/kde4/l10n/it):/usr/local/share/doc/HTML/it/step/examples.docbook
> /usr/local/share/doc/HTML/it/step/index.cache.bz2
> /usr/local/share/doc/HTML/it/step/index.docbook
> /usr/local/share/doc/HTML/it/step/tutorials.docbook
> /usr/local/share/locale/it/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-ja-4.14.3p4
> (x11/kde4/l10n/ja):/usr/local/share/locale/ja/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-kk-4.14.3p4
> (x11/kde4/l10n/kk):/usr/local/share/locale/kk/LC_MESSAGES/step.mo
> Warning: step-18.08.2 conflicts with kde-l10n-k
Re: [NEW]fonts/mada
George Rosamond writes: > pkg/DESCR: > > Mada is a modernist, low-contrast Arabic typeface based largely on > the typeface seen in Cairo metro old signage which was designed by > Professor Fathi Gouda of Faculty of Applied Arts, Helwan University. > > Mada is characterised by low descenders, open contours and low- > contrast forms making it suitable for small point sizes, user > interfaces, signage or low resolution settings. > > Mada can work also as a display typeface giving modernist and > simplistic feeling. > > Mada comes in 7 weights (ExtraLight, Light, Regular, Medium, SemiBold, > Bold and Black), as well as an interpolatable variable font that > can provide any intermediate weight on the fly. Two small things. One, DESCR is a little narrow. 80-ish columns would be better. > MASTER_SITES = https://github.com/alif-type/mada/archive/ We prefer "/releases/download/" URLs if they exist, and one exists for this port (Mada-1.3.zip on the releases page). The reason is that "/archive/" tarballs are generated on the fly and do not have stable checksums. With those two small changes, this is ok with me. -- Anthony J. Bentley
Re: [NEW]fonts/tagmukay
George Rosamond writes: > This is a font used for the Berber language, common in north Africa. > > Full pkg/DESCR: > > Tagmukay is a Shifinagh script font with support for the Tawallammat > Tamajaq language. The script name is more commonly spelled Tifinagh, > but Shifinagh is the preferred spelling in the region where Tawallammat > Tamajaq is spoken. Tagmukay is a Unicode font that features > bi-consonant ligatures and alternate forms necessary to support > this language. > > This port contains both TrueType and Web fonts. License marker has a typo: s/SIL OFT/SIL OFL/ DESCR is narrow. No biggie. This is port is ok with me with the typo fixed. -- Anthony J. Bentley
