Re: Preferred way of repocopy in terms of git

On Mon, 10 May 2021 09:30:56 +0200 Mathieu Arnold wrote: > On Fri, May 07, 2021 at 11:32:48PM +0600, Muhammad Moinur Rahman wrote: >> What is the preferred way of doing ports repocopy in git? In the hard >> way I can see moving it into two locations and merging them. But is >> there any easier way

Re: /usr/ports/print/ghostscript9-agpl-base gs_ll3.ps: Error: /undefinedresource (fwd)

On Tue, 04 May 2021 22:01:46 +0200 "Julian H. Stacey" wrote: >> Delete all those .pkgsave files. These are backups created by pkg when >> it has to install a file over an existing file. It means a previous >> version of ghostscript wasn't deleted properly. > > Thanks Coosemans, I ran my compa

Re: /usr/ports/print/ghostscript9-agpl-base gs_ll3.ps: Error: /undefinedresource (fwd)

On Tue, 04 May 2021 16:29:47 +0200 "Julian H. Stacey" wrote: > Hi ports@ people, > I wrote this to doc...@freebsd.org Sun, 02 May 2021 23:43:44 +0200 > but no reply by Tue May 4 16:26:48 CEST 2021. > Have others seen similar or got ideas to fix gs ghostscript ? > --- > > Hi doc...@freebs

Re: Call for testing: LibreOffice 7.1.1 release

On Mon, 8 Mar 2021 21:13:25 +1000 Dima Panov wrote: > gt3 vcl is not fully complete yet ans we (team) prefer to keep qt5 as default What is missing then? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports

Re: Call for testing: LibreOffice 7.1.1 release

On Fri, 5 Mar 2021 01:16:40 +1000 Dima Panov wrote: > Hello! > > LibreOffice 7.1.1 release is out and office@FreeBSD team calls everyone > interested to join us in testing cycle > > Our WIP repository available at GitHub, > https://github.com/freebsd/freebsd-ports-libreoffice. > Of course, we

Re: How should follks migrate from linux_base-c6 to linux_base-c7?

On Tue, 31 Dec 2019 05:28:39 -0800 David Wolfskill wrote: > As noted in > , > the -c6 ports "expire tomorrow." > > I don't see a documented process for migrating from linux_base-c6 to > linux_base-c7; perhaps I'm being thicker than

Re: dos2unix patch?

On Thu, 12 Sep 2019 14:23:58 +0900 Koichiro Iwao wrote: > is it possible to run dos2unix to patches fetched from PATCH_SITES? > or how can I change order of patch and dos2unix. > > I would like to apply dos2unix-ed patches to dos2unix-ed source. > Alternatively, applying patch first and then runn

Re: libgcc_s.so.1, Fortran, and the world (was: FreeCAD 0.17 && /lib//libgcc_s.so.1)

oth >>> ports, viz. his work on arm and powerpc, and upstream) and toolchain@! >>> >>> On Sun, 24 Feb 2019, Tijl Coosemans wrote: >>>> GCC_4.3.0 instead of GCC_3.3.0. The gcc commit that changed this >>>> doesn't explain why this was done,

Re: libgcc_s.so.1, Fortran, and the world (was: FreeCAD 0.17 && /lib//libgcc_s.so.1)

On Mon, 8 Apr 2019 13:16:15 +0800 (WITA) Gerald Pfeifer wrote: > This patch make 3 the default for gfortran. s/make/makes/ but otherwise the patch looks fine. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-

Re: loose dependency

On Thu, 14 Mar 2019 11:20:09 -0600 Adam Weinberger wrote: > On Thu, Mar 14, 2019 at 10:41 AM Koichiro Iwao wrote: >> On Thu, Mar 14, 2019 at 02:33:30PM +0100, Tijl Coosemans wrote: >>> Like hrs already said: since this is a build dependency you can just >>> w

Re: loose dependency

On Thu, 14 Mar 2019 19:09:40 +0900 Koichiro Iwao wrote: > On Thu, Mar 14, 2019 at 04:50:18PM +0900, Hiroki Sato wrote: >> That is a workaround while increasing maintenance cost. It is at the >> maintainer's discretion. > > Thanks for the advice. Fortunely, icons are not updated too open. The > m

Re: Building qt5-gui port?

On Tue, 12 Mar 2019 14:01:18 -0300 Lucas Nali de Magalhães wrote: >> On Feb 11, 2019, at 2:05 PM, Steve Kargl >> wrote: >>> On Mon, Feb 11, 2019 at 10:08:08AM +0100, Tijl Coosemans wrote: >>> On Sun, 10 Feb 2019 15:18:20 -0800 Steve Kargl >>> wrote: >&g

Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

On Sat, 23 Feb 2019 13:31:17 -0500 Diane Bruce wrote: > On Sat, Feb 23, 2019 at 10:52:03AM +, Dima Pasechnik wrote: >> On Sat, Feb 23, 2019 at 12:07 AM Steve Kargl >> wrote: >>> On Sat, Feb 23, 2019 at 09:19:01AM +1100, Dave Horsfall wrote: >>>> On F

Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

On Fri, 22 Feb 2019 19:14:33 +0200 Konstantin Belousov wrote: > On Fri, Feb 22, 2019 at 05:09:59PM +0100, Tijl Coosemans wrote: >> 1) GCC can add new symbols or new versions of them with every release >> which means the problem can reappear with every new GCC release and GCC >

Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

On Fri, 22 Feb 2019 08:44:54 -0800 Steve Kargl wrote: > On Fri, Feb 22, 2019 at 05:09:59PM +0100, Tijl Coosemans wrote: >> On Fri, 22 Feb 2019 15:39:17 +0200 Konstantin Belousov >>> Do you agree that the ultimate and proper solution is to add missed symbols >>> and versi

Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

On Fri, 22 Feb 2019 09:19:54 -0700 "Russell L. Carter" wrote: > On 2/22/19 6:04 AM, Tijl Coosemans wrote: >> As for Linux, note that in theory the same problem also exists there. >> It's just that most Linux distribution only provide one version of gcc. > >

Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

On Thu, 21 Feb 2019 10:24:51 -0800 Steve Kargl wrote: > On Thu, Feb 21, 2019 at 06:05:15PM +0100, Tijl Coosemans wrote: >> There's also the fact that gfortran behaves differently from the C >> compilers (both clang and gcc) when it comes to libgcc_s. Gfortran >> always l

Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

On Fri, 22 Feb 2019 15:39:17 +0200 Konstantin Belousov wrote: > Yes, we absolutely must avoid situation where two similar libraries > (i.e. providing some subset of symbols from other) are linked into the > same executing process. > > I think your patches would be a definitive improvement, esp. t

Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

On Thu, 21 Feb 2019 10:53:00 -0700 "Russell L. Carter" wrote: > On 2/21/19 10:05 AM, Tijl Coosemans wrote: >> On Sun, 17 Feb 2019 10:16:04 -0500 Diane Bruce wrote: >>> On Sat, Feb 16, 2019 at 06:35:52PM -0700, Russell L. Carter wrote: >>>> So

Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

On Thu, 21 Feb 2019 16:13:15 -0800 Steve Kargl wrote: > On Thu, Feb 21, 2019 at 11:18:50PM +0100, Tijl Coosemans wrote: >> On Thu, 21 Feb 2019 13:30:41 -0500 Diane Bruce wrote: >>> On Thu, Feb 21, 2019 at 06:05:15PM +0100, Tijl Coosemans wrote: >>>> On Sun, 17 Feb 2

Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

On Thu, 21 Feb 2019 13:30:41 -0500 Diane Bruce wrote: > On Thu, Feb 21, 2019 at 06:05:15PM +0100, Tijl Coosemans wrote: >> On Sun, 17 Feb 2019 10:16:04 -0500 Diane Bruce wrote: >>> Except python doesn't have an rpath which is why this keeps coming >>> up over a

Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

On Sun, 17 Feb 2019 10:16:04 -0500 Diane Bruce wrote: > On Sat, Feb 16, 2019 at 06:35:52PM -0700, Russell L. Carter wrote: >> So I must dig deeper. Perhaps with rpaths interacting with the system >> paths? > > You got it. ;) > Except python doesn't have an rpath which is why this keeps coming >

Re: Building qt5-gui port?

On Sun, 10 Feb 2019 15:18:20 -0800 Steve Kargl wrote: > On Sun, Feb 10, 2019 at 03:14:15PM -0800, Mark Millard wrote: >> >> /usr/ports/Mk/Uses/qt-dist.mk has: >> >> .if ${ARCH} == i386 && empty(MACHINE_CPU:Msse2) >> CONFIGURE_ARGS+=-no-sse2 >> .endif > > Hmmm. Oh well. I set C

Re: japanese/libreoffice build failed (13.0-CURRENT/r339677)

On Fri, 23 Nov 2018 17:00:05 +0900 KIRIYAMA Kazuhiko wrote: > I've update to r485516 and build japanese/libreoffice > again. Result was perfect! I've built with 'make > package-recursive' and all packages depends it had created > completely [1]. Thanks for maintaining japanese/libreoffice :-) >

Re: japanese/libreoffice build failed (13.0-CURRENT/r339677)

On Wed, 14 Nov 2018 21:06:37 +0900 KIRIYAMA Kazuhiko wrote: > er-statement -Wvla -Wpointer-arith -Wmissing-declarations > -Wmissing-prototypes -Wredundant-decls -Wundef -Wwrite-strings > -Wformat-nonliteral -Wformat-security -Winit-self -Wmissing-include-dirs > -Waddress -Wno-multichar -Wneste

Re: Inkscape compiles but crashes on startup

On Sat, 3 Nov 2018 22:31:34 -0700 bob prohaska wrote: > On Sat, Nov 03, 2018 at 07:18:52AM +0100, Walter Schwarzenfeld wrote: >> Wait, fix of the primal cause of it is committed right now. >> >> https://svnweb.freebsd.org/ports?view=revision&revision=483878 > > Alas, no luck. Updating the ports

Re: Firefox constantly trashing disk

On Fri, 14 Sep 2018 18:13:57 +0200 Andrea Venturoli wrote: > Hello. > > I think FireFox (ESR) on my system makes really too much disk I/O. > My profile is on an NFS drive, but I hear local disks spinning, so I > guess it's writing to /tmp or /var/tmp (or another local folder). > > Looks like an

Re: DEFAULT_VERSIONS=gcc=8 results in gfortran7

On Fri, 17 Aug 2018 10:24:53 + Anton Shterenlikht wrote: > I got no replies from fortran@, reposting here. > > I'm building with synth. > jrmarino says this should work, > i.e. the problem is not in synth. > > I have DEFAULT_VERSIONS=gcc=8 in synth make.conf: > > # cat /usr/local/etc/synth/

Re: Automake creation error.. generic or just me?

On Wed, 25 Jul 2018 22:43:05 +0800 Julian Elischer wrote: > I'm not exactly sure where the error come from.. possibly the find, if > stderr and stdout are not synchronous. > > Has anyone else seen this?  or understand it? > > > ===>  Building for automake-1.16.1 > --- doc/aclocal.1 --- > ---