On 9/12/15 2:01 AM, Kurt Jaeger wrote:
Hi!
Right now, I'm in the part where it tries to link the
build/external/v8_3.30.33.16/build/out
stuff and fails because the clang loader does not handle
liba files 8-(
The latest .shar is available at
Hey, any luck with this port?
>Tom Pusateri writes:
>
>> Here’s the Makefile
>>
>> PORTNAME=libchromiumcontent
>> PORTVERSION= 43.0.2357.65
>
>To override these variables you have to modify master port to use ?=.
>And altering PORTNAME often breaks master's DISTFILES/WRKSRC/etc.
>
>In this
Hi!
> Right now, I'm in the part where it tries to link the
> build/external/v8_3.30.33.16/build/out
> stuff and fails because the clang loader does not handle
> liba files 8-(
The latest .shar is available at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203043
together with a
Dear Maintainer,
I just wanted to let you know that the output for htop (after
installation) is out of order:
Message for htop-1.0.3:
***
htop(1) requires linprocfs(5) to be mounted. If you don't
have it mounted already, please add this
On Sat, 12 Sep 2015 01:46:23 +0200
Michelle Sullivan wrote:
> Roger Marquis wrote:
> > RW via freebsd-ports wrote:
> >> It needs both. It won't use just the pid file because the pid
> >> might have been reassigned to another process if the original
> >> daemon died without deleting its pid file.
RW via freebsd-ports wrote:
You'd rather an rc script fails at run-time and shuts down the wrong
daemon than fail when the script is being developed?
It's not so much where the script fails than that it fails in the first
place. Neither a pidfile nor a command_interpreter needs to be required
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,
