On Mon, Aug 31, 2020 at 08:35:59AM -0700, bob prohaska wrote:
>
> In the meantime a clean restart is going, it looks like firefox
> got bumped to version 80. Perhaps that'll make a difference. To
> conserve resources I'm using a plain vanilla make. If use of a
> ports management system is mandator
On 9/1/20 8:13 PM, Willem Jan Withagen wrote:
> Hi,
>
> In my ceph port one of the maintainers added this to
>
> USE_PYTHON= cython py3kplist
>
> But I'm trying to find out what it does?
> And it is not (yet) on the USE_PYTHON page in the ports handbook.
It's documented in Mk/Uses/python.mk
Hi,
In my ceph port one of the maintainers added this to
USE_PYTHON= cython py3kplist
But I'm trying to find out what it does?
And it is not (yet) on the USE_PYTHON page in the ports handbook.
--WjW
___
freebsd-ports@freebsd.org mailing list
http
Hi!
> net-p2p/gtk-gnutella https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247914
This one fails on i386 current. See the PR itself for details.
--
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-ports@freebsd.org
On 2020-09-01 11:46, Bob Eager wrote:
Almost certainly the -fno-common problem with clang 11.
This now defaults to -fno-common, which causes multiply defined symbols
at link time if something is declared global in more than one module
(instead of extern in all but one module). There is a similar
On Mon, 31 Aug 2020 20:33:34 +0200
Wolfram Schneider wrote:
> On Wed, 26 Aug 2020 at 18:50, Kurt Jaeger wrote:
> >
> > Hi!
> >
> > > > man.cgi has provisions for most of this already, it's only
> > > > missing some job to regulary extract the latest
> > > >
> > > > ftp://ftp.freebsd.org/pub
Almost certainly the -fno-common problem with clang 11.
This now defaults to -fno-common, which causes multiply defined symbols
at link time if something is declared global in more than one module
(instead of extern in all but one module). There is a similar problem
with gcc.
Declaring -fno-commo
Hi there
I have received a number of messages from pkg-fallout regarding the port I
maintain, and pkg-fallout maintains that my port is broken.
The really strange thing here is that I am able to build it in all the
versions up till 13.0-CURRENT.
The port builds without any errors. Any one with a
Hi!
> P.S. Apologies for using the word "ignored" - it's an emotive word, and
> that wasn't the intent - I didn't mean it in a critical way.
Well, the correct word would be 'drowned' 8-} Those PRs drowned
in the flood of PRs -- and the committers drowned with them 8-}
At least the rtc one is com
P.S. Apologies for using the word "ignored" - it's an emotive word, and
that wasn't the intent - I didn't mean it in a critical way.
Cheers, Jamie
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsu
There are updates to 2 ports that are not being actioned - one of the ports has
since
been marked for deletion as it no longer works, and the fix is almost 2 years
old! (I
updated the fix a few months ago)
How do I go about getting these actioned?
emulators/rtc https://bugs.freebsd.org/bugzilla
11 matches
Mail list logo