Re: qemu-x86_64-static has target_freebsd_flock being too small (__packed use issue) [subject correction: fixed to be "too small"]

2019-01-04 Thread Mark Millard via freebsd-ports
[Just correcting the "larger" to be "smaller".] On 2019-Jan-4, at 19:29, Mark Millard wrote: [qemu-aarch64-static has the same problem but qemu-armv7-sstatic does not. The context here is FreeBSD head -r341836 based and ports head -r488859 based.] Note: I assume that "struct target_freebsd_flo

qemu-x86_64-static has target_freebsd_flock being too large (__packed use issue)

2019-01-04 Thread Mark Millard via freebsd-ports
[qemu-aarch64-static has the same problem but qemu-armv7-sstatic does not. The context here is FreeBSD head -r341836 based and ports head -r488859 based.] Note: I assume that "struct target_freebsd_flock" is meant to match the memory layout of the target's native "struct flock". Otherwise the re

qemu-x86_64-static has target_msghdr's msg_controllen field with the wrong size so its msg_flags is at the wrong offset and target_msghdr is too large

2019-01-04 Thread Mark Millard via freebsd-ports
[qemu-aarch64-static has the same problem but qemu-armv7-sstatic does not. The context here is FreeBSD head -r341836 based and ports head -r488859 based.] Note: I assume that "struct target_msghdr" is meant to match the memory layout of the target's native "struct msghdr". Otherwise the reported

Re: How much memory to compile www/chromium?

2019-01-04 Thread bob prohaska
> > On 2019-Jan-1, at 10:21, bob prohaska wrote: > > > On Tue, Dec 18, 2018 at 09:49:03AM -0800, bob prohaska wrote: > >> > >> Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile > >> successfully over > >> several days. The -DBATCH option was used, in hopes it'd fetch the right

FreeBSD ports you maintain which are out of date

2019-01-04 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you

Re: FreeBSD Port: lang/ocaml

2019-01-04 Thread Kurt Jaeger
Hi! > Current version of ocaml is 4.02.3, but newest is 4.07. > Could ocaml port be updated to newest version please? The attempt to do so can be followed at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218333 -- p...@freebsd.org +49 171 3101372 One year to go ! _

FreeBSD Port: lang/ocaml

2019-01-04 Thread Serpent7776
Hello, Current version of ocaml is 4.02.3, but newest is 4.07. Could ocaml port be updated to newest version please? -- /* * Serpent7776 */ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscr