On 3/8/12, Mark Linimon wrote:
> On Wed, Mar 07, 2012 at 12:11:52PM +, b. f. wrote:
>> The custom gcc article that you are attempting to use was written at
>> a time when some of the related port Makefiles had some shortcomings
>> that no longer exist, and is not the recommended way to use lan
On Wed, Mar 07, 2012 at 12:11:52PM +, b. f. wrote:
> The custom gcc article that you are attempting to use was written at
> a time when some of the related port Makefiles had some shortcomings
> that no longer exist, and is not the recommended way to use lang/gcc*
> for ports.
Would you be int
On Wed, Mar 07, 2012 at 06:19:51PM +0200, Andriy Gapon wrote:
> BTW, our traditional taxonomy seems to be: "USE_XXX" is for stuff that ports
> really require, "WITH_XXX" is for user preferences.
This isn't a taxonomy suggestion, it's a documented requirement:
http://www.freebsd.org/doc/en_US.ISO8
On 3/7/2012 23:44, Baptiste Daroussin wrote:
> On Wed, Mar 07, 2012 at 11:56:17PM +0300, Alexander Churanov wrote:
>> Folks,
>>
>> I've read the conversation on ports/156253 ("Update devel/boost-* from
>> 1.45 to 1.46.1") and decided to share current status of my work.
>>
>> I have a patch for upda
On Wed, Mar 07, 2012 at 11:56:17PM +0300, Alexander Churanov wrote:
> fail for other reasons
> deskutils/kdepim4
> editors/koffice-kde4
> editors/libreoffice
Marking these as broken isn't really an option (especially the first
one). A lot more people rely on KDE than need the boost update.
Hi,
On 3/7/2012 22:48, Michael Heitmeier wrote:
> I just cvsupped ports so I'm wondering is that a problem on my side or is
> the port broken?
> ===>>> Port directory: /usr/ports/www/p5-libwww
>
> ===>>> Launching 'make checksum' for www/p5-libwww in background
> ===>>> Gathering dependency lis
On Wed, 07 Mar 2012 16:48:02 -0600, Philip M. Gollucci
wrote:
On 03/07/12 22:03, Mark Felder wrote:
How does the community feel about having multiple mariadb ports like our
current mysql ports? It would be nice to have mariadb53-{client-server}
and mariadb55-{client|server} as well, in my op
On Wed, Mar 07, 2012 at 11:56:17PM +0300, Alexander Churanov wrote:
> Folks,
>
> I've read the conversation on ports/156253 ("Update devel/boost-* from
> 1.45 to 1.46.1") and decided to share current status of my work.
>
> I have a patch for updating Boost to 1.48.0.
> http://alexanderchuranov.co
On 03/07/12 22:03, Mark Felder wrote:
> How does the community feel about having multiple mariadb ports like our
> current mysql ports? It would be nice to have mariadb53-{client-server}
> and mariadb55-{client|server} as well, in my opinion.
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164072
On 3/7/12, Andriy Gapon wrote:
> on 07/03/2012 14:11 b. f. said the following:
>> you can just
>> install lang/gcc or lang/gcc46 and set USE_GCC=4.6 in your build
>> environment, an included Makefile, or on the command line
>
> BTW, our traditional taxonomy seems to be: "USE_XXX" is for stuff that
Hi,
I'm trying to upgrade squeezeboxserver using portmaster and after a short
while it seems to loop for net/p5-Net-HTTP (p5-libwww-5.837) like the
following.
I just cvsupped ports so I'm wondering is that a problem on my side or is
the port broken?
Cheers,
Michael
===>>> Port directory: /usr/p
How does the community feel about having multiple mariadb ports like our
current mysql ports? It would be nice to have mariadb53-{client-server}
and mariadb55-{client|server} as well, in my opinion.
Thoughts?
___
freebsd-ports@freebsd.org mailing l
Folks,
I've read the conversation on ports/156253 ("Update devel/boost-* from
1.45 to 1.46.1") and decided to share current status of my work.
I have a patch for updating Boost to 1.48.0.
http://alexanderchuranov.com/boost-port/boost-145-to-148-v05.diff
Yes, I know that 1.19 is already released.
Hello,
I've added you to my furfq group at Yahoo! Groups, a free,
easy-to-use service. Yahoo! Groups makes it easy to send and receive
group messages, coordinate events, share photos and files, and more.
Description of the group:
on 07/03/2012 14:11 b. f. said the following:
> you can just
> install lang/gcc or lang/gcc46 and set USE_GCC=4.6 in your build
> environment, an included Makefile, or on the command line
BTW, our traditional taxonomy seems to be: "USE_XXX" is for stuff that ports
really require, "WITH_XXX" is for
On 03/07/12 09:28, lini...@freebsd.org wrote:
As part of an ongoing effort to reduce the number of problems in
[...]
portname: x11/kdelibs3
broken because: does not compile
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=x11&por
Hello,
Maybe there are some problems with freennx and nxserver. Compile OK,
Authentication OK, but session failed. Forums say the same. I
use the last FreeBSD 9, on i386 machine.
nxserver on Ports is quite old: 2.x.
For amd64 platform nxserver isn't even availeble.
Is it possible to update freen
On 3/6/2012 1:51 AM, Doug Barton wrote:
> On 3/5/2012 6:13 AM, Lee Dilkie wrote:
>> Is the handbook going to be updated with a confirmed procedure?
> The preferred procedure has always been to delete everything and
> reinstall. Do you see anywhere in the handbook where it says anything
> differen
> Adding dinoex (Maintainer of graphics/png).
>
> On Mon, Feb 27, 2012 at 9:51 PM, Gautam wrote:
>
> >
> >
> >> Still didnt work for me -- did another buildworld and retried to check if
> > there was something else messed up.
> >
> > I am moving back to base gcc for now. Waiting for redports lang/
Roman Bogorodskiy wrote:
>> USE_AUTOTOOLS= libtool
>> USE_GNOME= ltverhack
>>
>> to avoid bumping.
>
> I'm using it and it doesn't help: libgnutls.so.47 becomes
> libgnutls.so.48 (where 48 is 'current').
Probably you have not set LIBTOOLFILES to include all the 'configure'
scripts.
In any
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
24 matches
Mail list logo
