Hi Hackers,
I made a new port named /deve/bear, which is a tool that generates a
compilation database for clang tooling. It is useful for
clang-tidy/clang-check with non-cmake project.
PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220475
WWW: https://github.com/rizsotto/Bear
QA:
portlin
Hi!
> make makeplist
[...]
You have to redirect hat into the pkg-plist file, like this:
make makeplist > new-plist
Then edit to fix issues (there's always one to force
you to visually inspect the file 8-)
vi new-plist
and name the final file pkg-plist.
--
p...@opsec.eu+49 171 31
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 All,
Could someone committer please have a look at this?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214758.
--
Best regards,
Nikolay
signature.asc
Description: OpenPGP digital signature
Am 12.07.17 um 07:42 schrieb Rainer Hurling:
> Hi duglas@
>
> I had the same problem. I completely solved it by rebuilding the
> dependency chain of devel/subversion:
>
> portmaster serf-1.3.9_1 expat-2.2.1 gettext-runtime-0.19.8.1_1
> apr-1.5.2.1.5.4_2 sqlite3-3.19.3_1 subversion-1.9.6
>
> Prob
I'm starting using synth, never used it before.
I get this error:
# synth build net/mpich
Error opening terminal: xterm.
I'm supposed to run synth as root, right?
Is synth trying to open another xterm as root?
I've never allowed root access to a display:
# xterm
Warning: This program is an sui
Thank you all kindly for you input.
I'd not previously set any locale at all. Setting my locale in
~/.login_conf as below enables me to run svn updates again.
me:\
:charset=UTF-8:\
:lang=en_AU.UTF-8:\
:setenv=LC_COLLATE=C:
I chose my lang by checking the output from,
l
Hello Folks
I have been trying to update the glusterfs port to bring it up to the
latest version 3.11.1
I would appreciate if folks would build and install the port... test
and report back any issues.
The glusterfs client needs FreeBSD 11.1-RC2 or later (fuse fixed in
r320451)
Tarball or diff a
Hello,
I'm trying to build packages on an rpi3, on a freshly build image (with
crochet), and when it's trying to build pkg from ports, I'm getting the
following error message:
libtool: link: cc -D_BSD_SOURCE -I../libpkg -I../libpkg -I../compat
-I../external/libucl/klib -I../external/uthash -I../
On Tuesday, 11 July 2017 08:47:17 Bob Willcox wrote:
> Hmm, I just tried running synth on my test system again (this is the system
> that I successfully built and install texinfo on just a bit ago) and synth
> still fails with the same build errors as before. I'm not all that familiar
> with synth,
Am 12.07.17 um 18:11 schrieb David Naylor:
> On Tuesday, 11 July 2017 08:47:17 Bob Willcox wrote:
>> Hmm, I just tried running synth on my test system again (this is the system
>> that I successfully built and install texinfo on just a bit ago) and synth
>> still fails with the same build errors as
from Anton Shterenlikht:
> I'm starting using synth, never used it before.
> I get this error:
> # synth build net/mpich
> Error opening terminal: xterm.
> I'm supposed to run synth as root, right?
> Is synth trying to open another xterm as root?
> I've never allowed root access to a display:
On 7/12/2017 7:59 AM, Anton Shterenlikht wrote:
I'm starting using synth, never used it before.
I get this error:
# synth build net/mpich
Error opening terminal: xterm.
as a regular user open xterm
then do the fololwing
su -
synth just-build /net/mpich
or if you have doas and doas configured
> From: Baho Utot
> Date: Wed, 12 Jul 2017 21:09:11 -0400
>
>
>
> On 7/12/2017 7:59 AM, Anton Shterenlikht wrote:
> > I'm starting using synth, never used it before.
> > I get this error:
> >
> > # synth build net/mpich
> > Error opening terminal: xterm.
> as a regular user open xterm
> then do th
I upgraded my Alpine to 2.21 (from 2.20) recently, now it is no longer
displaying UTF-8 characters (yes, I have it set). Anyone else noticed
this? I need to know whether it's a port bug or an upstream bug, so I
know who to beat up.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand s
15 matches
Mail list logo