Hi!
> On Nov 27, r486043 was committed to head to fix several vulnerabilities
> in the Samba 4.7 and 4.8 ports, but it wasn't merged to 2018Q4. A PR
> was opened, but 2018Q4 sat unfixed until it expired at the end of the year.
>
> Filing a PR didn't help. Mentioning the PR on this list didn't
Hi, Reference:
> From: Kubilay Kocak
> Reply-to: ko...@freebsd.org
> Date: Wed, 2 Jan 2019 15:50:53 +1100
Kubilay Kocak wrote:
> On 2/01/2019 2:21 pm, Julian H. Stacey wrote:
> > Hi ports@
> > anyone else seen this or have ideas please:
> > chrome
> > ld-elf.so.1: /usr/local/l
[I was wrong: it is code elimination, not motion. volatile is
not a fix.]
On 2019-Jan-1, at 19:37, Mark Millard wrote:
> [It looks to me like the assembler code has some code moved out of the
> loop that it should not be (by intent). It appears that calling
> tcmpset_32 does not prevent code mot
On 2/01/2019 2:21 pm, Julian H. Stacey wrote:
Hi ports@
anyone else seen this or have ideas please:
chrome
ld-elf.so.1: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ"
uname 13.0-CURRENT
/usr/src/.svn_revision 342578
ls -l /usr/local/lib/libglib*
lrwxr-xr-x 1 root wheel 21 N
[It looks to me like the assembler code has some code moved out of the
loop that it should not be (by intent). It appears that calling
tcmpset_32 does not prevent code motion to before the call and
the variable involved was not declared volatile.]
On 2019-Jan-1, at 18:43, Mark Millard wrote:
> T
Hi ports@
anyone else seen this or have ideas please:
chrome
ld-elf.so.1: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ"
uname 13.0-CURRENT
/usr/src/.svn_revision 342578
ls -l /usr/local/lib/libglib*
lrwxr-xr-x 1 root wheel 21 Nov 13 02:21
/usr/local/lib/libglib-1.2.so.0@ -
The below showed up for poudiere-devel bulk getting stuck using one FreeBSD
cpu while building graphics/poppler-qt5 . This is not a kevent hang-up, unlike
the last hang-up that I analyzed. I do not yet know how repeatable this is
but the original hang-up and the one experiment the below is from.
>
On Nov 27, r486043 was committed to head to fix several vulnerabilities
in the Samba 4.7 and 4.8 ports, but it wasn't merged to 2018Q4. A PR
was opened, but 2018Q4 sat unfixed until it expired at the end of the year.
Filing a PR didn't help. Mentioning the PR on this list didn't help.
What c
On Tue, Jan 01, 2019 at 03:14:26PM -0800, Mark Millard wrote:
>
>
> On 2019-Jan-1, at 10:21, bob prohaska wrote:
>
> > On Tue, Dec 18, 2018 at 09:49:03AM -0800, bob prohaska wrote:
> >
> >
> > As a further test, I'ved added two additional USB flash swap devices and am
> > re-running
> > the
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
>> options.
>
I'm curious whether the default Vim port should use GTK2 or GTK3 as
its UI toolkit, but I use neither so I need input from people here.
Right now it defaults to GTK2, but I'm suspecting that more people use
GTK3 these days. I haven't run X in about 10 years, so I don't really
know one way or the o
Hi!
> > > I have found the real cause of most of the problems: it's ccache
> > > configuration.
> >
> > Thanks for the update. I've never used ccache, but I've changed my
> > setup to test this 8-}
>
> I've been bitten by this in the past with that exact scenario, except
> it also slowed the amd
On Tue, Jan 1, 2019 at 11:22 AM Kurt Jaeger wrote:
>
> Hi!
>
> > I have found the real cause of most of the problems: it's ccache
> > configuration.
>
> Thanks for the update. I've never used ccache, but I've changed my
> setup to test this 8-}
I've been bitten by this in the past with that exac
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
> options.
>
Just for fun I added a mechanical hard disk with a 4 G
Hi!
> I have found the real cause of most of the problems: it's ccache
> configuration.
Thanks for the update. I've never used ccache, but I've changed my
setup to test this 8-}
--
p...@freebsd.org +49 171 3101372 One year to go !
___
> > Hi!
> >
> > > > SSD or spinning drives ?
> > > >
> > > > > I have 3.6 Gb of RAM and 2 Gb of swap.
> > > >
> > > > Run top and check the state of ARC.
> > > > I think it needs much more RAM.
> > >
> > > I don't think it is a SSD (it has cylinders, sectors etc.).
> > > If you can tell me a way to
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
Hi,
The 2019Q1 branch has been created. It means that the next update on the
quarterly packages will be on the 2019Q1 branch.
A lot of things happened in the last three months:
- pkg 1.10.5_5
- New default version for LLVM (70)
- Default version of GCC switched to 8
- Default version of Perl swit
> Hi!
>
> > > SSD or spinning drives ?
> > >
> > > > I have 3.6 Gb of RAM and 2 Gb of swap.
> > >
> > > Run top and check the state of ARC.
> > > I think it needs much more RAM.
> >
> > I don't think it is a SSD (it has cylinders, sectors etc.).
> > If you can tell me a way to check it I will be gl
[Note: My armv7 context builds ports with -mcpu=cortex-a7 via a make.conf
like file. The in-use world also was built with -mcpu=cortex-a7 .]
In order to avoid the likes of:
. . .
as -meabi=5 --defsym ARCHITECTURE=7 -march=armv7-a -mfloat-abi=hard -mfpu=neon
-I./ -I"/wrkdirs/usr/ports/multimedia
20 matches
Mail list logo