On Thu, Sep 13, 2012 at 08:21:31AM +0200, Pietro Cerutti wrote:
> On 2012-Sep-11, 23:29, Doug Barton wrote:
> > What we need to do is what I and others have been asking to do for
> > years. We need to designate a modern version of gcc (no less than 4.6)
> > as the official default ports compiler, a
On 2012-Sep-11, 23:29, Doug Barton wrote:
> What we need to do is what I and others have been asking to do for
> years. We need to designate a modern version of gcc (no less than 4.6)
> as the official default ports compiler, and rework whatever is needed to
> support this. Fortunately, that goal i
Doug Barton writes:
> On 09/11/2012 02:52 AM, Erik Cederstrand wrote:
>> So can we do a sweep on the ports tree and mark the 2232 ports with
>> USE_GCC=4.2 until they can actually build with clang?
>
> Unfortunately it isn't that simple. We already have a statistically
> significant number of po
Dimitry Andric writes:
> Now, as to how we can convince CMake to put the -I/usr/local/include at
> the end... Maybe we should just patch the CMakeLists.txt, but that is a
> rather ugly solution. :)
Try using
CPPFLAGS+=-isystem${LOCALBASE}/include
gcc(1) (and clang) has a flag for
Hello Sales,
I am interested in purchasing some of your products which i saw on your web
site, I will like to know if you can ship directly to AUSTRALIA, I also want
you to know my mode of payment for this order is via T/T letter of Credit. Get
back to me if you can ship to that destination
On Wed, Sep 12, 2012 at 10:59 PM, Doug Barton wrote:
> On 9/12/2012 1:22 AM, Jerry wrote:
>> On Tue, 11 Sep 2012 23:29:27 -1000
>> Doug Barton articulated:
>>
>>> What we need to do is what I and others have been asking to do for
>>> years. We need to designate a modern version of gcc (no less tha
On 6 September 2012 14:33, Bryan Drewery wrote:
> On 9/5/2012 11:57 PM, Cy Schubert wrote:
>> Hi all,
>>
>> I'm considering a -devel port which checks out from our upline's VCS repo,
>> also generating a dynamic plist. I'm sure this is possible. Are there any
>> examples of this?
>>
>>
>
> AFAIK i
On 9/12/2012 1:22 AM, Jerry wrote:
> On Tue, 11 Sep 2012 23:29:27 -1000
> Doug Barton articulated:
>
>> What we need to do is what I and others have been asking to do for
>> years. We need to designate a modern version of gcc (no less than 4.6)
>> as the official default ports compiler, and rework
On 9/12/2012 12:40 AM, Erik Cederstrand wrote:
> Den 12/09/2012 kl. 11.29 skrev Doug Barton :
>
>> On 09/11/2012 02:52 AM, Erik Cederstrand wrote:
>>> So can we do a sweep on the ports tree and mark the 2232 ports
>>> with USE_GCC=4.2 until they can actually build with clang?
>>
>> Unfortunately
On Wed, 12 Sep 2012 12:36:47 +0200
Ján Šebošík wrote:
> Hi all
>
> while I was trying to build ports/mail/postfix, the problem occured
> in file ./work/postfix-2.9.4/src/global/dict_ldap.c.
>
> Here is my Postfix port configuration (FYI: LDAP is compiled with SASL
> support - both client & serv
On Wed, 12 Sep 2012 21:48:52 +0200
"Herbert J. Skuhra" wrote:
> On Wed, 12 Sep 2012 12:36:47 +0200
> Ján Šebošík wrote:
>
> > Hi all
> >
> > while I was trying to build ports/mail/postfix, the problem occured
> > in file ./work/postfix-2.9.4/src/global/dict_ldap.c.
> >
> > Here is my Postfix
--- On Wed, 9/12/12, Chris Rees wrote:
> From: Chris Rees
> Subject: Re: [HEADS-UP] Announcing the end of port CVS
> To: "Jeffrey Bouquet"
> Cc: "Beat Gaetzi" , freebsd-ports@freebsd.org
> Date: Wednesday, September 12, 2012, 12:07 PM
> On 12 September 2012 15:14, Jeffrey
> Bouquet
> wrote:
2012/9/9 Kevin Oberman :
> 5. svn co http://svn0.us-west.freebsd.org/ports/head /usr/ports
>OR
>svn co http://svn0.us-east.freebsd.org/ports/head /usr/ports
Why not use svn.freebsd.org ? Maybe it could use geodns someday, like portsnap ?
--
Olivier Smedts
On 12 September 2012 15:14, Jeffrey Bouquet wrote:
>
> --- On Wed, 9/12/12, Jeffrey Bouquet wrote:
>
>> From: Jeffrey Bouquet
>> Subject: Re: [HEADS-UP] Announcing the end of port CVS
>> To: freebsd-ports@FreeBSD.org, "Beat Gaetzi"
>> Date: Wednesday, September 12, 2012, 6:31 AM
>>
>>
>> --- On
On Wed, Sep 12, 2012 at 03:03:43PM +0200, Lars Engels wrote:
> two of the ports I maintain don't build with CLANG, yet. I
> just checked that on the wiki page [1].
To repeat myself, the ports I've listed on that page are the "big
problems". People need to look at the errorlogs URLs up at the
top
--- On Wed, 9/12/12, Jeffrey Bouquet wrote:
> From: Jeffrey Bouquet
> Subject: Re: [HEADS-UP] Announcing the end of port CVS
> To: freebsd-ports@FreeBSD.org, "Beat Gaetzi"
> Date: Wednesday, September 12, 2012, 6:31 AM
>
>
> --- On Fri, 9/7/12, Beat Gaetzi
> wrote:
>
> > From: Beat Gaetzi
--- On Fri, 9/7/12, Beat Gaetzi wrote:
> From: Beat Gaetzi
> Subject: [HEADS-UP] Announcing the end of port CVS
> To: freebsd-ports@FreeBSD.org
> Date: Friday, September 7, 2012, 5:36 AM
> The development of FreeBSD ports is
> done in Subversion nowadays.
> For the sake of compatibility a Subv
On Wed, Sep 12, 2012 at 04:15:20AM -0500, Mark Linimon wrote:
> On Tue, Sep 11, 2012 at 11:27:50AM +0200, Lars Engels wrote:
> > At the moment the ports maintainers don't give much about if their ports
> > build with CLANG or not because they're not forced to.
>
> I think this is a mis-representat
On Tue, 11 Sep 2012 23:29:27 -1000
Doug Barton articulated:
> What we need to do is what I and others have been asking to do for
> years. We need to designate a modern version of gcc (no less than 4.6)
> as the official default ports compiler, and rework whatever is needed
> to support this. Fortu
Den 12/09/2012 kl. 11.29 skrev Doug Barton :
> On 09/11/2012 02:52 AM, Erik Cederstrand wrote:
>> So can we do a sweep on the ports tree and mark the 2232 ports with
>> USE_GCC=4.2 until they can actually build with clang?
>
> Unfortunately it isn't that simple. We already have a statistically
>
Hi all
while I was trying to build ports/mail/postfix, the problem occured
in file ./work/postfix-2.9.4/src/global/dict_ldap.c.
Here is my Postfix port configuration (FYI: LDAP is compiled with SASL
support - both client & server):
root@s1:/home/devel/ports/mail/postfix # make showconfig
===>
Having trouble viewing this email? Click here to view online
http://oomph.digitalwelly.com/t/r-e-kyjkjyk-yktdlhdtyh-x/
Dear Customer
Whether your Finance business has grown and your space isn't quite working for
you or you'd like to create a more innovative environment to inspire your team,
De
On 09/11/2012 11:15 PM, Mark Linimon wrote:
> On Tue, Sep 11, 2012 at 11:27:50AM +0200, Lars Engels wrote:
>> At the moment the ports maintainers don't give much about if their ports
>> build with CLANG or not because they're not forced to.
>
> I think this is a mis-representation.
>
> Adding the
On 09/11/2012 02:52 AM, Erik Cederstrand wrote:
> So can we do a sweep on the ports tree and mark the 2232 ports with
> USE_GCC=4.2 until they can actually build with clang?
Unfortunately it isn't that simple. We already have a statistically
significant number of ports that don't even compile wit
On 12 Sep 2012, at 10:15, Mark Linimon wrote:
> On Tue, Sep 11, 2012 at 11:27:50AM +0200, Lars Engels wrote:
>> At the moment the ports maintainers don't give much about if their ports
>> build with CLANG or not because they're not forced to.
>
> I think this is a mis-representation.
>
> Addin
On Tue, Sep 11, 2012 at 11:27:50AM +0200, Lars Engels wrote:
> At the moment the ports maintainers don't give much about if their ports
> build with CLANG or not because they're not forced to.
I think this is a mis-representation.
Adding the requirement "your ports must work on clang" is adding a
On 09/11/2012 05:58 AM, Pedro F. Giffuni wrote:
> Hello guys;
>
>
> - Original Message -
> ...
>>
>> 2012/9/11 Doug Barton :
>>> Now that we have a new version of libxul in the ports tree, any plans of
>>> upgrading swt to take advantage of it? I'd love to get the
>>> vulnerabilities
27 matches
Mail list logo
