Re: Problems with out libgcc_s.so in base

On 19/08/2016 10:13, Steven G. Kargl wrote: On Fri, Aug 19, 2016 at 01:14:32AM +0200, Tijl Coosemans wrote: On Thu, 18 Aug 2016 14:48:28 +0200 Dimitry Andric wrote: how would you solve the problem of having multiple, possibly incompatible versions of the same library in different directories?

Re: Problems with out libgcc_s.so in base

On Fri, 19 Aug 2016 10:28:14 +0300 Konstantin Belousov wrote: > The option which would fix all this mess is: > 1. add rpath for gcc lib/ directory into spec file > and > 2. make ports collection use its own compiler instead of fighting with >the base. That still doesn't cover all cases, e.g.

RE: Updating pidgin-sipe FreeBSD port

Have been following the bug link you posted, Walter. Just wanted to thank you again for your time and effort. Looking forward to testing the new version. Anindya ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freeb

Re: how did BSD libc make binary compatibility promise beetween freebsd version?

On 19/08/2016 15:39, kang joni wrote: > As the title suggest, I usually compile my linux code from old debian > squeeze to run for either centos 6 or debian wheezy and these distros > later version and adjusting some app rpath and clang libc++ runtime > libs to point local relative file path via or

Re: how did BSD libc make binary compatibility promise beetween freebsd version?

If you mean using libc/libc++ API in FreeBSD with no break, This is what FreeBSD provides by symbol versioning to provide same/compatible API in different versions. This means If you have a program that uses an API [printf(3) for example] on FreeBSD 9, and a change made on that API in FreeBSD 10,

how did BSD libc make binary compatibility promise beetween freebsd version?

As the title suggest, I usually compile my linux code from old debian squeeze to run for either centos 6 or debian wheezy and these distros later version and adjusting some app rpath and clang libc++ runtime libs to point local relative file path via origin method. Is there any easy guideline to fo

Re: question about Makefile from net/abills

> > +--On 19 août 2016 11:59:20 +0200 Jochen Neumeister > wrote: > | Hi there, > | > | I'm just trying to port net/abills. > | > | Now, i testing the port with portlint: > | > |# portlint > | WARN: Makefile: possible use of absolute pathname "/usr/abills". > | WARN: Makefile: possible use of ab

Re: question about Makefile from net/abills

+--On 19 août 2016 11:59:20 +0200 Jochen Neumeister wrote: | Hi there, | | I'm just trying to port net/abills. | | Now, i testing the port with portlint: | |# portlint | WARN: Makefile: possible use of absolute pathname "/usr/abills". | WARN: Makefile: possible use of absolute pathname "/usr/

question about Makefile from net/abills

Hi there, I'm just trying to port net/abills. Now, i testing the port with portlint: # portlint WARN: Makefile: possible use of absolute pathname "/usr/abills". WARN: Makefile: possible use of absolute pathname "/usr/bin/perl". 0 fatal errors and 2 warnings found. Now my question: how can I wr

FreeBSD ports you maintain which are out of date

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: Problems with out libgcc_s.so in base

On Fri, Aug 19, 2016 at 01:14:32AM +0200, Tijl Coosemans wrote: > On Thu, 18 Aug 2016 14:48:28 +0200 Dimitry Andric wrote: > > On 18 Aug 2016, at 11:15, Tijl Coosemans wrote: > >> On Wed, 17 Aug 2016 14:17:10 -0700 Steve Kargl > >> wrote: > >>> % gfortran6 -o z foo.f90 && ./z > >>> /lib/libgcc