On Sat, Jan 11, 2014 at 1:09 PM, Bernhard Fröhlich wrote:
> I still think this is the wrong approach and I won't maintain all those
> clang patches in the official port. The problem that I see is that we are
> diverging from upstream vbox too much and end up maintaining a very special
> usecase an
On Sat, Jan 11, 2014 at 1:09 PM, Bernhard Fröhlich wrote:
>
> Am 11.01.2014 03:49 schrieb "Craig Rodrigues" :
>
> > (5) Build and install gsoap from jkim's port (you need to do this
> because the version of gsoap in the ports tree will result in failed
> compilation):
> >
> > cd /tmp/xy/jkim/dev
Am 11.01.2014 03:49 schrieb "Craig Rodrigues" :
>
> Hi,
>
> I had problems with the virtualbox-ose-4.22 port
> under FreeBSD 10.0-RC5, where VirtualBox would occasionally
> crash.
> It looks like the mix of QT C++ libraries compiled with clang,
> vs. the virtualbox-ose port compiled with g++46 was
I have been running this on a weekly basis for a while just to make sure I
don't get caught out if a disk fails. For a few weeks now, it seems to run
without completing.
Here's where it seems to be right now.
74824 root 1 1190 3300K 1336K RUN 0 19.9H 100.00%
dump
I rotat
On Sat, Jan 11, 2014 at 12:46 PM, Tijl Coosemans wrote:
> The problem is pdftk-2.02. You need pdftk-2.02_1 for which a package
> has been built already so it should be on the pkg mirrors soon.
Bingo! That fixed the problem! Thank you!!! :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
_
On 01/11/14 10:39, Ports Index build wrote:
> Dear port maintainers,
>
> The following list includes ports maintained by you that have duplicate
> LATEST_LINK values. They should either be modified to use a unique
> PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is
> deprecated.
Dear port maintainers,
The following list includes ports maintained by you that have duplicate
LATEST_LINK values. They should either be modified to use a unique
PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is
deprecated. See the portmgr blog post for more information:
http://
On Sat, Jan 11, 2014 at 12:21 PM, Boris Samorodov wrote:
> It's not a solution but a workaround which helped me. Run the following
> command to find out which installed packages need gcc46 (note it's a
> one line command):
> -
> % for o in `pkg info -aoq`; do \[ \! -z `pkg query %dn-%dv -o $o
On Sat, 11 Jan 2014 11:37:50 +0100 CeDeROM wrote:
> On Sat, Jan 11, 2014 at 11:29 AM, CeDeROM wrote:
>> On Sat, Jan 11, 2014 at 3:18 AM, Gerald Pfeifer wrote:
>>> Wait a minute: is one of yoir ports hard coding lang/gcc46 instead of
>>> doing USE_GCC? If so, here is the bug.
>
> Here goes the fu
11.01.2014 14:37, CeDeROM пишет:
> On Sat, Jan 11, 2014 at 11:29 AM, CeDeROM wrote:
>> On Sat, Jan 11, 2014 at 3:18 AM, Gerald Pfeifer wrote:
>>> Wait a minute: is one of yoir ports hard coding lang/gcc46 instead of doing
>>> USE_GCC? If so, here is the bug.
>>> Gerald
>
> Here goes the full ou
On Sat, Jan 11, 2014 at 11:29 AM, CeDeROM wrote:
> On Sat, Jan 11, 2014 at 3:18 AM, Gerald Pfeifer wrote:
>> Wait a minute: is one of yoir ports hard coding lang/gcc46 instead of doing
>> USE_GCC? If so, here is the bug.
>> Gerald
Here goes the full ouput of the "pkg upgrade" maybe it will help
On Sat, Jan 11, 2014 at 3:18 AM, Gerald Pfeifer wrote:
> Wait a minute: is one of yoir ports hard coding lang/gcc46 instead of doing
> USE_GCC? If so, here is the bug.
> Gerald
Yes, it seems so, as I only installed packages from binaries and the
gcc was the dependency, I did not install gcc46 by
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
13 matches
Mail list logo
