The port lyx-1.4.2 is broken on current and has been for awhile:
In file included from /usr/local/include/boost/test/utils/nullstream.hpp:23,
from ../../src/support/debugstream.h:17,
from ../../src/debug.h:16,
from math_extern.C:34:
/usr/local/incl
Please see the attached port updated to 2.3.0 - of course up-to-date
patches are not yet avaiable for SPF and VDA so it won't compile with
those options, and these options should be removed to prevent accidental
use from scripts/configure.postfix and distinfo for official
distribution. Working
Dejan Lesjak wrote:
Therefore, I doubt that such "pull the trigger" approach is really going
to work in this case. Some more gradual course is in due: with X11R6
being banned as a target for a new ports, with new GNOME version moving
to the LOCALBASE and so on.
I seem to have phrased my mail a
On Thu, 13 Jul 2006 18:43:01 +0200
Heino Tiedemann <[EMAIL PROTECTED]> wrote:
> Alexander Leidinger <[EMAIL PROTECTED]> wrote:
>
> > Quoting Heino Tiedemann <[EMAIL PROTECTED]> (from Thu, 13 Jul
> > 2006 15:23:07 +0200):
> >
> >> I just wanted to so a simple »portupgrade mplayer-gtk«, and see wha
On Thu, 2006-07-13 at 23:58 -0700, Maxim Sobolev wrote:
> What's the gain? Transition will be a really big PITA for most existing
> users. Everybody who would be trying to install a KDE/GNOME or even a
> general X11 port after a switchover still having all X11 bits in
> /usr/X11R6 is likely to b
--- Mark Linimon <[EMAIL PROTECTED]> ha scritto:
> On Fri, Jul 14, 2006 at 09:17:56PM +0200, [EMAIL PROTECTED] wrote:
> > but life is already pretty hard for people wanting to use
> > XFree86 (no packages for KDE, GNOME, etc...)
>
> We simply don't have the horsepower on the build cluster, or d
Brooks Davis wrote:
> Assuming we deal with all the conflicting ports in the first round
> I don't fully buy this argument. If most people can simply upgrade
> the ports in question then "rm -rf /usr/X11RC && ln -s /usr/local
> /usr/X11R6" will take care of config files. That's admittedly a larg
Dejan Lesjak wrote:
> Actually, I didn't mean the prefix that some port installs into would be the
> truble, rather where given port looks for includes, libraries and other files
> from ports that it depends upon.
But that's all part of the same issue. If the port is prefix-clean, than
this won
On Friday 14 July 2006 21:33, Doug Barton wrote:
> Dejan Lesjak wrote:
> > On Friday 14 July 2006 08:58, Maxim Sobolev wrote:
> >> What's the gain?
> >
> > I believe I mentioned some of gains in first mail. There is also the
> > benefit of less divergence to upstreams as ./configure scripts of vari
On Fri, Jul 14, 2006 at 12:33:22PM -0700, Doug Barton wrote:
> Dejan Lesjak wrote:
> > On Friday 14 July 2006 08:58, Maxim Sobolev wrote:
> >> What's the gain?
> >
> > I believe I mentioned some of gains in first mail. There is also the
> > benefit
> > of less divergence to upstreams as ./confi
On Fri, Jul 14, 2006 at 09:17:56PM +0200, [EMAIL PROTECTED] wrote:
> but life is already pretty hard for people wanting to use
> XFree86 (no packages for KDE, GNOME, etc...)
We simply don't have the horsepower on the build cluster, or disk space on
the mirrors, to support this. It takes 5 days to
Dejan Lesjak wrote:
> On Friday 14 July 2006 08:58, Maxim Sobolev wrote:
>> What's the gain?
>
> I believe I mentioned some of gains in first mail. There is also the benefit
> of less divergence to upstreams as ./configure scripts of various ports
> use /usr/local as default prefix, but more im
--- michael johnson <[EMAIL PROTECTED]> ha scritto:
...
>
>
> for the few people this would apply to they could always add something to
> make.conf to install Xfree86 in /usr/X11R6 or xorg or what ever and have
> both installed.
>
Of course X11BASE can still be more documented in the section
On 7/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
--- Jeremy Messenger <[EMAIL PROTECTED]> ha scritto:
>
> Nobody should install both xorg and xfree86 at the same time. It's
pretty
> pointless and it would cause more messy when you try to build other
ports
> that depend on either of it
--- Jeremy Messenger <[EMAIL PROTECTED]> ha scritto:
>
> Nobody should install both xorg and xfree86 at the same time. It's pretty
> pointless and it would cause more messy when you try to build other ports
> that depend on either of it. Move everything in LOCALBASE, nothing more
> and n
Heino Tiedemann wrote:
> I found 2 Solutions fpr the permissions:
>
>
> Solution a)
>
> ,
> | I've added the following to /etc/devfs.conf:
> | own lpt0root:cups
> | permlpt00660
> `
>
>
>
> Solution b)
> ,
> | Add following lines to /etc/devfs.rules:
> |
> | [syst
On Fri, 14 Jul 2006 09:09:27 -0500, <[EMAIL PROTECTED]> wrote:
Hello;
--- Dejan Lesjak <[EMAIL PROTECTED]> ha scritto:
On Friday 14 July 2006 01:59, [EMAIL PROTECTED] wrote:
> Hi;
>
> Just here mumbling...
>
> It would be interesting to set
>
> X11BASE=/usr/X11 when using XFree86 and
> X1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When testing this patch I get the following error:
===> Registering installation for lua-5.0.2_1
===> Returning to build of tolua++-1.0.92
===> Configuring for tolua++-1.0.92
===> Building for tolua++-1.0.92
scons: Reading SConscript files ...
T
I'm working on porting libdssialsacompat to FreeBSD so that
the dssi plugin distribution might compile (this should open up
the possibility of quite a lot more audio software being ported
to FreeBSD) but I'm having trouble. I've never created a port
before, so bare with me...
--Makefile--
# New p
On Jul 13, 2006, at 4:51 PM, Benjamin Lutz wrote:
On Thursday 13 July 2006 04:29, lveax wrote:
vmware server 1.0 was released and free for download,there are
windows
and linux version,would anyone bring the linux version to freebsd
ports?
Unlikely to happen, since VMWare uses a linux kerne
Hello;
--- Dejan Lesjak <[EMAIL PROTECTED]> ha scritto:
> On Friday 14 July 2006 01:59, [EMAIL PROTECTED] wrote:
> > Hi;
> >
> > Just here mumbling...
> >
> > It would be interesting to set
> >
> > X11BASE=/usr/X11 when using XFree86 and
> > X11BASE=${LOCALBASE} when using XOrg.
> >
> > Not
On Friday 14 July 2006 01:59, [EMAIL PROTECTED] wrote:
> Hi;
>
> Just here mumbling...
>
> It would be interesting to set
>
> X11BASE=/usr/X11 when using XFree86 and
> X11BASE=${LOCALBASE} when using XOrg.
>
> Not only due to historical consistency (/usr/X11 is the path recommended in
> XFree86
On Friday 14 July 2006 08:58, Maxim Sobolev wrote:
> What's the gain?
I believe I mentioned some of gains in first mail. There is also the benefit
of less divergence to upstreams as ./configure scripts of various ports
use /usr/local as default prefix, but more importantly as modular X.org is
Dear porters,
This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is
http://people.freebsd.org/~fenner/errorlogs/
so you can easily check the status of ports that you maintain. In
addition, the li
On Fri, 14 Jul 2006, [LoN]Kamikaze wrote:
>> I believe that if you do a
>>
>> % pkg_info | grep ldap
>>
>> you will find packages different from openldap-client, and if you remove
>> all (or some) of these, the Wine build will succeed.
>>
>> Looking at upstream changes, it looks as if some th
Gerald Pfeifer wrote:
> On Tue, 11 Jul 2006, [LoN]Kamikaze wrote:
>> The latest version of the port fails with the following output on my
>> system (FBSD 6.1):
>>
>> cc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT
>> -fPIC -Wall -pipe -fno-strict-aliasing -gstabs+
>> -
On Thu, 2006-07-13 at 23:58 -0700, Maxim Sobolev wrote:
> What's the gain? Transition will be a really big PITA for most existing
> users. Everybody who would be trying to install a KDE/GNOME or even a
> general X11 port after a switchover still having all X11 bits in
> /usr/X11R6 is likely to b
What's the gain? Transition will be a really big PITA for most existing
users. Everybody who would be trying to install a KDE/GNOME or even a
general X11 port after a switchover still having all X11 bits in
/usr/X11R6 is likely to be screwed on build time, due to mismatching
includes/libraries
28 matches
Mail list logo
