Re: aarch64 bulk build report
On Sat, Sep 30, 2017 at 03:06:02AM -0600, phess...@openbsd.org wrote: > bulk build on arm64.ports.openbsd.org > started on Fri Sep 8 11:23:32 MDT 2017 > finished at Sat Sep 30 03:05:09 MDT 2017 > lasted 22D08h41m > done with kern.version=OpenBSD 6.2-beta (GENERIC) #3: Fri Sep 8 05:14:33 MDT > 2017 > > built packages:8005 > Sep 8:352 > Sep 9:333 > Sep 10:920 > Sep 11:1 > Sep 12:2 > Sep 16:53 > Sep 17:1765 > Sep 18:558 > Sep 19:761 > Sep 26:859 > Sep 27:796 > Sep 28:464 > Sep 29:1140 > > > build failures: 232 > http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lzip/clzip.log > http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lzip/lzip.log > http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lzip/lziprecover.log > http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lzip/pdlzip.log > http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lzip/plzip.log /usr/sbin/pkg_add -aI -Dunsigned -Drepair lunzip-1.9 lzlib-1.9 Error: /dev/sd0m is not large enough (/var/db/pkg/lunzip-1.9/+DESC) When you fix that problem, the lzip programs will build fine. > http://build-failures.rhaalovely.net//aarch64/2017-09-08/lang/gambit.log MAXSSIZ is ((paddr_t)8*1024*1024) on arm64. OK? diff -r 4480970ebbd6 Makefile --- MakefileFri Sep 29 23:36:03 2017 + +++ MakefileSun Oct 01 04:29:21 2017 +0200 @@ -3,6 +3,7 @@ COMMENT= complete, efficient and reliable implementation of Scheme V= 4.8.8 +REVISION= 0 DISTNAME= gambit-v${V:S/./_/g} PKGNAME= gambit-$V API_V= ${V:R:S/./0/}00${V:E} @@ -30,10 +31,8 @@ MAKE_FILE= ${WRKSRC}/makefile -# On sparc64, gcc crashes with the default stack limit: -# "cc: Internal error: Illegal instruction" on _gambc.c do-build: - ulimit -s 12288 && cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} \ + ulimit -s ${STACK_SIZE} && cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} \ ${MAKE_PROGRAM} ${MAKE_FLAGS} -f ${MAKE_FILE} ${ALL_TARGET} do-test: @@ -46,4 +45,12 @@ CFLAGS += -O0 .endif +# On sparc64, gcc crashes with the default stack limit: +# "cc: Internal error: Illegal instruction" on _gambc.c +.if ${MACHINE_ARCH} == "sparc64" +STACK_SIZE = 12288 +.else +STACK_SIZE = 8192 +.endif + .include
Re: ports broken on clang archs
On Fri, Sep 29, 2017 at 06:40:03PM +0100, Stuart Henderson wrote: > On 2017/09/29 18:50, Jeremie Courreges-Anglas wrote: > > I moved texmacs, avidemux and ti-msp430-gcc to COMPILER=base-gcc. > > Thanks. > > > graphics/asymptote is affected too: > > > > NOT_FOR_ARCHS= ${CLANG_ARCHS} # hangs during build, while > > running > > # ../asy -dir ../base -config "" -render=0 -f pdf -noprc cube.asy > > # in WRKSRC/doc. run the abovef command with -vvv for more info. > > # this does not fail with ports clang, though. > > Oh I think we could do "base-gcc ports-clang" here now that we have it... Note that in my experience, most of the clang "failures" are actually code that has undefined behavior, and thus fails.
Re: NEW: games/soyuz
On 2017/09/30 00:41, Ian Sutton wrote: > Hello, I've ported some software. > > http://ce.gl/soyuz-port.tgz > > games/soyuz is a spaceflight simulator used to train Soviet cosmonauts > to fly fourth generation Soyuz rockets in the mid-to-late 1980s, it was > designed and written by members of the Soviet space program. It > specifically simulates the instrumentation and control interface for the > descent module re-entering the atmosphere, and provides a virtual > interface that functionally matches hardware found in real-life Soyuz modules. > > Here are some screenshots: > > https://ce.gl/soyuz/ > > It passes portcheck: > > 0 $ pwd > /usr/ports/games/soyuz > 0 $ /usr/ports/infrastructure/bin/portcheck > games/soyuz > > However I'm not very experienced with writing ports and would appreciate > feedback. > > > PS - I'd be interested in hearing from anyone who manages to land, > because this is beyond difficult :) > > Ian > Diff on top to tidy it up a bit. I don't read Russian (totally killing my chances of being an astronaut ;) but is there something on the screen you get by pressing T that would pass for a version number? Is there copyright information anywhere that would let us fill in the markers better? (btw, it's easier to review if you send a tar with just portname/* rather than usr/ports/category/portname/* .. or category/portname/* if there are multiple ports in different categories within one submission). Interesting idea to use dosbox in the port like this :-) diff --git Makefile Makefile index f499718..c40031e 100644 --- Makefile +++ Makefile @@ -1,51 +1,35 @@ # $OpenBSD$ -COMMENT = Training program for the Soyuz-TMA spacecraft. -DISTNAME = soyuz-1.0 -CATEGORIES = games +COMMENT = training program for the Soyuz-TMA spacecraft + +PKGNAME = soyuz-1.0 +DISTNAME = soyuz +DISTSUBDIR = ${PKGNAME} +EXTRACT_SUFX = .zip -DISTFILES =soyuz.zip -DISTFILES += soyuz.conf -DISTFILES += soyuz.sh +CATEGORIES = games MAINTAINER = Ian Sutton-PERMIT_PACKAGE_CDROM = N/A +# no license information? +PERMIT_PACKAGE_CDROM = no license information? PERMIT_PACKAGE_FTP = Yes -MASTER_SITES = https://ce.gl/ports/dist/soyuz/ +HOMEPAGE = https://archive.org/details/demo211 -EXTRACT_SUFX = .zip -EXTRACT_ONLY = soyuz.zip +MASTER_SITES = https://ce.gl/ports/dist/soyuz/ -BUILD_DEPENDS =archivers/unzip -RUN_DEPENDS = emulators/dosbox +RUN_DEPENDS = emulators/dosbox -NO_BUILD = Yes -NO_TEST = Yes -NO_CONFIGURE = Yes +NO_BUILD = Yes +NO_TEST = Yes +WRKDIST = ${WRKDIR} do-install: - mkdir ${PREFIX}/libexec/soyuz/ - install -D -c -m 755 -o root -g bin \ -${WRKDIR}/COLOR.SF ${PREFIX}/libexec/soyuz/ - install -D -c -m 755 -o root -g bin \ -${WRKDIR}/EPROM.DAT ${PREFIX}/libexec/soyuz/ - install -D -c -m 755 -o root -g bin \ -${WRKDIR}/EPROMSPS.DAT ${PREFIX}/libexec/soyuz/ - install -D -c -m 755 -o root -g bin \ -${WRKDIR}/INPU.EXE ${PREFIX}/libexec/soyuz/ - install -D -c -m 755 -o root -g bin \ -${WRKDIR}/KS020.DAT ${PREFIX}/libexec/soyuz/ - install -D -c -m 755 -o root -g bin \ -${WRKDIR}/MODEL.DAT ${PREFIX}/libexec/soyuz/ - install -D -c -m 755 -o root -g bin \ -${WRKDIR}/MONO.SF ${PREFIX}/libexec/soyuz/ - install -D -c -m 755 -o root -g bin \ -${WRKDIR}/RUNTIME.WP ${PREFIX}/libexec/soyuz/ - install -D -c -m 755 -o root -g bin ${DISTDIR}/soyuz.sh ${PREFIX}/bin/soyuz - install -D -c -m 755 -o root -g bin ${DISTDIR}/soyuz.conf \ - ${PREFIX}/libexec/soyuz/soyuz.conf - + ${INSTALL_DATA_DIR} ${PREFIX}/libexec/soyuz/ + cd ${WRKDIR}; ${INSTALL_DATA} COLOR.SF EPROM.DAT EPROMSPS.DAT \ + INPU.EXE KS020.DAT MODEL.DAT MONO.SF RUNTIME.WP \ + ${FILESDIR}/soyuz.conf ${PREFIX}/libexec/soyuz/ + ${INSTALL_SCRIPT} ${FILESDIR}/soyuz.sh ${PREFIX}/bin/soyuz .include
Re: zbar, python module import core dumps
On 2017/09/30 13:00, Jonathan Gray wrote: > On Fri, Sep 29, 2017 at 04:07:08PM -0400, Jiri B wrote: > > Hi, > > > > this simple things make python core dump. Anything more for this > > issue report I could provide? > > > > Jiri > > > > # python2.7 -c 'import zbar' > > Segmentation fault (core dumped) > > Here is a patch from debian that seems to avoid the crash. > I never used the python api back when I actually used zbar. OK for after unlock. > You will need to create the patches directory before applying it. patch -p0 does that automatically, by the way. > Index: Makefile > === > RCS file: /cvs/ports/graphics/zbar/Makefile,v > retrieving revision 1.24 > diff -u -p -r1.24 Makefile > --- Makefile 17 Jun 2017 11:36:16 - 1.24 > +++ Makefile 30 Sep 2017 02:52:00 - > @@ -2,7 +2,7 @@ > > COMMENT= ZBar barcode reader > DISTNAME=zbar-0.10 > -REVISION=16 > +REVISION=17 > > SHARED_LIBS= zbar0.0 \ > zbargtk 0.0 > --- /dev/null Sat Sep 30 12:55:41 2017 > +++ patches/patch-python_imagescanner_c Sat Sep 30 12:53:24 2017 > @@ -0,0 +1,15 @@ > +$OpenBSD$ > + > +Index: python/imagescanner.c > +--- python/imagescanner.c.orig > python/imagescanner.c > +@@ -67,7 +67,8 @@ imagescanner_get_results (zbarImageScanner *self, > + } > + > + static PyGetSetDef imagescanner_getset[] = { > +-{ "results", (getter)imagescanner_get_results, }, > ++{ "results", (getter)imagescanner_get_results, NULL, NULL, NULL}, > ++{NULL} /* Sentinel */ > + }; > + > + static PyObject* >
Re: zbar, python module import core dumps
On Sat, Sep 30, 2017 at 01:00:11PM +1000, Jonathan Gray wrote: > > # python2.7 -c 'import zbar' > > Segmentation fault (core dumped) > > Here is a patch from debian that seems to avoid the crash. > I never used the python api back when I actually used zbar. Thank you, works OK on amd64. Tested with qrtools[1] to decode a sample QR code from internet. [1] https://ralgozino.wordpress.com/2011/06/13/how-to-create-and-decode-a-qr-code-in-python-using-qrtools/ Jiri
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rob...@cvs.openbsd.org 2017/09/30 04:05:44 Modified files: mail/kopano: Makefile.inc mail/kopano/core: distinfo Log message: kopano seems to automatically recreate their tarballs all the time so let's use my own mirror for a "stable" distfile
aarch64 bulk build report
bulk build on arm64.ports.openbsd.org started on Fri Sep 8 11:23:32 MDT 2017 finished at Sat Sep 30 03:05:09 MDT 2017 lasted 22D08h41m done with kern.version=OpenBSD 6.2-beta (GENERIC) #3: Fri Sep 8 05:14:33 MDT 2017 built packages:8005 Sep 8:352 Sep 9:333 Sep 10:920 Sep 11:1 Sep 12:2 Sep 16:53 Sep 17:1765 Sep 18:558 Sep 19:761 Sep 26:859 Sep 27:796 Sep 28:464 Sep 29:1140 build failures: 232 http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/gcpio.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/geteltorito.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/gshar+gunshar.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/gtar,static.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/ha.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/innoextract.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lxsplit.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lz4json.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lzip/clzip.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lzip/lzip.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lzip/lziprecover.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lzip/pdlzip.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/lzip/plzip.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/macutil.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/makeself.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/nulib.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/p5-Compress-LZO.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/p5-PerlIO-gzip.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/par1cmdline.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/pecl-lzf.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/pecl-rar.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/pigz.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/py-lzo.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/sltar.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/snappy.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/ucl.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/unarj.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/unshield.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/unzip,iconv.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/xdms.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/zopfli.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/archivers/zstd.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/ansiweather.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/celestia.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/dgpsip.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/gcal.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/jday.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/libnova.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/luna.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/phoon.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/py-metar.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/sattrack.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/sunclock.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/wmglobe.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/wmmoonclock.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/wmspaceweather.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/wmsun.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/xearth.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/xephem.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/xphoon.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/astro/xworld.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/audio/abcde.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/audio/adplug.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/audio/alac_decoder.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/audio/ario.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/audio/ascd.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/audio/aubio.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/audio/aucatctl.log http://build-failures.rhaalovely.net//aarch64/2017-09-08/audio/audacious-plugins.log