Re: Clang as default compiler November 4th
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, and rework whatever is needed to > > support this. Fortunately, that goal is much more easily achieved than > > fixing ports to build and run with clang. (It's harder than it sounds > > because there are certain key libs that define some paths depending on > > what compiler they were built with, but still easier than dealing with > > clang in the short term.) > > I like the idea very much. My only concern is that gcc is heavy to > build. Gerald has been advocating this for a while as well. In fact, he's just made a commit that makes the lang/gcc42 compiler much easier to bootstrap itself. There's a set of interlocking changes that we need to make to the infrastructure to modernize our compiler choices. I've been talking to Gerald about some of the aspects of it and hope to have something to propose fairly soon. But IMHO it's a little bit trickier than it appears at first glance. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clang as default compiler November 4th
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 is much more easily achieved than > fixing ports to build and run with clang. (It's harder than it sounds > because there are certain key libs that define some paths depending on > what compiler they were built with, but still easier than dealing with > clang in the short term.) I like the idea very much. My only concern is that gcc is heavy to build. I can't imagine booting into a freshly installed production machine and having to install gcc just to build the couple of ports that I need there. Unless we provide a fast shortcut way to have make depends install gcc via pkg when needed, or some similar mechanism.. -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpjvBufkSprf.pgp Description: PGP signature
Re: Clang as default compiler November 4th
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 ports that don't even compile with gcc 4.2.1. How
> many compilers do we expect the users to install? :)
>
> 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 is much more easily achieved than
> fixing ports to build and run with clang. (It's harder than it sounds
> because there are certain key libs that define some paths depending on
> what compiler they were built with, but still easier than dealing with
> clang in the short term.)
To that effect ports also need to respect CC/CXX. There were a few -exp
runs without /usr/bin/{cc,gcc,etc} to find out non-conforming ones as
part of ports/159117. However, the issue was quickly shoved under the
carpet in order to focus on the more important, clang as default.
# last try, assumes_gcc are ports ignoring CC/CXX, many are fixed
http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/index-reason.html
>
> Once that is done, the compiler in the base is an afterthought, and we
> can do away with gcc in the base altogether much more easily. Users who
> want to help support building ports with clang can continue to do so.
>
> Doug
--
Ignoring for the moment clang -exp runs are *still* done with clang 3.0
while we're discussing here clang 3.2 becoming default.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Help. Porting "FreeOCL" fails (atomic_ops.h missing, CLANG++ libc++ issues ...)
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 systems broken by design:
-isystem dir
Search dir for header files, after all directories specified by -I
but before the standard system directories. Mark it as a system
directory, so that it gets the same special treatment as is applied
to the standard system directories. If dir begins with "=", then
the "=" will be replaced by the sysroot prefix; see --sysroot and
-isysroot.
For example, firefox uses it to avoid picking up lang/spidermonkey headers.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Intl Shippment
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 and also if you accept the payment type indicated. Kindly get back to me so i can forward you the products i needed I await your quick response. >From the desk of Purchase manager, Company name:CPT CONCEPT INTL. Contact:Robert Corwin Artrage Complex 233 James St Northbridge, Perth WA 6003 Australia. Email:robert2cr...@gmail.com Tel:8 9227 62884 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clang as default compiler November 4th
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 than 4.6) >>> as the official default ports compiler, and rework whatever is needed >>> to support this. Fortunately, that goal is much more easily achieved >>> than fixing ports to build and run with clang. (It's harder than it >>> sounds because there are certain key libs that define some paths >>> depending on what compiler they were built with, but still easier >>> than dealing with clang in the short term.) >> >> That is a well thought out, highly intuitive and completely doable >> idea. Therefore it will be ignored. > > No, it'll be ignored because I suggested it. :) > >> It seems that the FreeBSD authors are more concerned with the >> licensing language of GCC than in getting a fully functioning port's >> compiler into the FreeBSD base system. > > Just to be clear, I'm not suggesting putting the "ports compiler" into > the base. I'm suggesting that it be managed as a port, just like pkg is. > This works fine for the ports that are already hard-coding compiler > dependencies, and mostly worked for me back when I get it a test run > when I made the suggestion years ago. The few glitches I (and others who > have done it since) ran into just need some elbow grease applied. > > By keeping ports-related things in the ports tree we gain a huge amount > of agility, and lose the concerns about licensing in the base. It's a > win/win. > > Doug > Three-ish things: a) Doesn't that remove all incentives for eventually converging on just one compiler (bar some specific exceptions)? a.1) Isn't that bad? b) Doesn't that mean that at some future point, we'll have to jump the ports compiler to a newer (probably much newer) version, with all the maintenance fun of that? c) I guess this still lets me use clang for most ports if I really wish to? (I've compiled most ports with clang for a while, and the speed + useful error messages would be hard to give up...) I'm not sure if those are big or small issues - probably a matter of taste. :) -- Daniel Nebdal ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Automatic Port
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 it had only been done with 1 port, and that has been reverted due > to not having a known distinfo. > > The preferred way is to just do snapshot updates. That way the user is > alerted to new versions. Otherwise they are sitting on this "" > version forever until they *force* reinstall to get an upgrade. > Hm, however, you could make a target to just update to latest snapshot. http://www.bayofrum.net/~crees/scratch/Makefile-snippet (imperfect, but you should get the idea). Best case scenario, make nextsnap && port test && svn commit ;) Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clang as default compiler November 4th
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 whatever is needed >> to support this. Fortunately, that goal is much more easily achieved >> than fixing ports to build and run with clang. (It's harder than it >> sounds because there are certain key libs that define some paths >> depending on what compiler they were built with, but still easier >> than dealing with clang in the short term.) > > That is a well thought out, highly intuitive and completely doable > idea. Therefore it will be ignored. No, it'll be ignored because I suggested it. :) > It seems that the FreeBSD authors are more concerned with the > licensing language of GCC than in getting a fully functioning port's > compiler into the FreeBSD base system. Just to be clear, I'm not suggesting putting the "ports compiler" into the base. I'm suggesting that it be managed as a port, just like pkg is. This works fine for the ports that are already hard-coding compiler dependencies, and mostly worked for me back when I get it a test run when I made the suggestion years ago. The few glitches I (and others who have done it since) ran into just need some elbow grease applied. By keeping ports-related things in the ports tree we gain a huge amount of agility, and lose the concerns about licensing in the base. It's a win/win. Doug ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clang as default compiler November 4th
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 it isn't that simple. We already have a >> statistically significant number of ports that don't even compile >> with gcc 4.2.1. How many compilers do we expect the users to >> install? :) > > If a port doesn't compile with the default compiler in base, I expect > that port to add a build dependency on the compiler that it actually > does compiles with. Yes, they do this now. The problem is that the set is growing, and the rate of growth is increasing. > Of course, I hope to not have 6 different > compilers installed on my system, but the list of build or runtime > dependencies are at the discretion of the port (maintainer). As you > (I think) said, we can't force port maintainers to patch their ports > to support clang. Those are unrelated issues. Please re-read the bits of my post that you snipped. The overwhelming majority of problems we have with compiling ports now would be fixed by having a modern version of gcc as the official (i.e., supported) "ports compiler." The clang efforts would be a parallel track. Doug ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Postfix and SASL compilation problem
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 & server): > > root@s1:/home/devel/ports/mail/postfix # make showconfig > ===> The following configuration options are available for postfix-2.9.4,1: > PCRE=on: Perl Compatible Regular Expressions > SASL2=off: Cyrus SASLv2 (Simple Auth. and Sec. Layer) > DOVECOT=off: Dovecot 1.x SASL authentication method > DOVECOT2=on: Dovecot 2.x SASL authentication method > SASLKRB5=off: If your SASL req. Kerberos5, select this > SASLKMIT=off: If your SASL req. MIT Kerberos5, select this > TLS=on: Enable SSL and TLS support > BDB=on: Berkeley DB (uses WITH_BDB_VER) > MYSQL=off: MySQL maps (uses WITH_MYSQL_VER) > PGSQL=off: PostgreSQL maps (uses DEFAULT_PGSQL_VER) > SQLITE=on: SQLite maps > OPENLDAP=on: OpenLDAP maps (uses WITH_OPENLDAP_VER) > LDAP_SASL=on: Enable OpenLDAP client-to-server SASL auth > CDB=off: CDB maps lookups > NIS=off: NIS maps lookups > VDA=on: VDA (Virtual Delivery Agent 32Bit) > TEST=off: SMTP/LMTP test server and generator > SPF=on: SPF support (via libspf2 1.2.x) > INST_BASE=off: Install into /usr and /etc/postfix > ===> Use 'make config' to modify these settings > > Line 232 in postfix-2.9.4/src/global/dict_ldap.c doesn't contain > proper path to sasl.h header file on FreeBSD. > Fixed line should look like this: #include > > Here is the patch: > ### > --- dict_ldap.c.old 2012-09-11 00:39:40.0 +0200 > +++ dict_ldap.c 2012-09-11 00:22:56.0 +0200 > @@ -229,7 +229,7 @@ >/* > * SASL headers, for sasl_interact_t. Either SASL v1 or v2 should be fine. > */ > -#include > +#include > #endif > ### This change will break WITH_SASL2. I think you only have to enable WITH_SASL2 when you use WITH_LDAP_SASL. Builds fine here. -- Herbert ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Postfix and SASL compilation problem
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 port configuration (FYI: LDAP is compiled with SASL > > support - both client & server): > > > > root@s1:/home/devel/ports/mail/postfix # make showconfig > > ===> The following configuration options are available for postfix-2.9.4,1: > > PCRE=on: Perl Compatible Regular Expressions > > SASL2=off: Cyrus SASLv2 (Simple Auth. and Sec. Layer) > > DOVECOT=off: Dovecot 1.x SASL authentication method > > DOVECOT2=on: Dovecot 2.x SASL authentication method > > SASLKRB5=off: If your SASL req. Kerberos5, select this > > SASLKMIT=off: If your SASL req. MIT Kerberos5, select this > > TLS=on: Enable SSL and TLS support > > BDB=on: Berkeley DB (uses WITH_BDB_VER) > > MYSQL=off: MySQL maps (uses WITH_MYSQL_VER) > > PGSQL=off: PostgreSQL maps (uses DEFAULT_PGSQL_VER) > > SQLITE=on: SQLite maps > > OPENLDAP=on: OpenLDAP maps (uses WITH_OPENLDAP_VER) > > LDAP_SASL=on: Enable OpenLDAP client-to-server SASL auth > > CDB=off: CDB maps lookups > > NIS=off: NIS maps lookups > > VDA=on: VDA (Virtual Delivery Agent 32Bit) > > TEST=off: SMTP/LMTP test server and generator > > SPF=on: SPF support (via libspf2 1.2.x) > > INST_BASE=off: Install into /usr and /etc/postfix > > ===> Use 'make config' to modify these settings > > > > Line 232 in postfix-2.9.4/src/global/dict_ldap.c doesn't contain > > proper path to sasl.h header file on FreeBSD. > > Fixed line should look like this: #include > > > > Here is the patch: > > ### > > --- dict_ldap.c.old 2012-09-11 00:39:40.0 +0200 > > +++ dict_ldap.c 2012-09-11 00:22:56.0 +0200 > > @@ -229,7 +229,7 @@ > >/* > > * SASL headers, for sasl_interact_t. Either SASL v1 or v2 should be > > fine. > > */ > > -#include > > +#include > > #endif > > ### > > This change will break WITH_SASL2. This is nonsense. Please ignore this part of my reply. :) > I think you only have to enable WITH_SASL2 when you use > WITH_LDAP_SASL. Builds fine here. -- Herbert ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS-UP] Announcing the end of port CVS
--- 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:
> >
> > --- 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
> >> > 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 Subversion to
> CVS
> >> exporter
> >> > is
> >> > in place which has some limitations. For
> CVSup
> >> mirroring
> >> > cvsup
> >> > based on Ezm3 is used which breaks regularly
> especially
> >> on
> >> > amd64
> >> > and with Clang and becomes more and more
> >> unmaintainable.
> >> >
> >> > For those reasons by February 28th 2013 the
> FreeBSD
> >> ports
> >> > tree will
> >> > no longer be exported to CVS. Therefore ports
> tree
> >> updates
> >> > via CVS
> >> > or CVSup will no longer available after that
> date. All
> >> users
> >> > who use
> >> > CVS or CVSup to update the ports tree are
> encouraged
> >> to
> >> > switch to
> >> > portsnap(8) [1] or for users which need more
> control
> >> over
> >> > their ports
> >> > collection checkout use Subversion directly:
> >> >
> >> > % svn co https://svn0.us-west.FreeBSD.org/ports/head /usr/ports
> >> >
> >> > and update a checked out repository using:
> >> >
> >> > % cd /usr/ports && svn update
> >> >
> >> > Advanced users, or larger sites, might
> consider setting
> >> up a
> >> > local
> >> > svn mirror. Both for people doing direct
> checkouts and
> >> for
> >> > people
> >> > wanting to use a local mirror, they can access
> one of
> >> the
> >> > public
> >> > subversion servers [2].
> >> >
> >> > How to set up a Subversion mirror using
> svnsync(1) is
> >> > described in
> >> > the FreeBSD Committers Guide [3]. Initial
> seeds to set
> >> up a
> >> > svnsync
> >> > mirror are provided on the FreeBSD FTP mirror
> sites
> >> under
> >> > /pub/FreeBSD/development/subversion/.
> >> >
> >> > Binary packages for pkg_install are still
> provided via
> >> the
> >> > FTP mirror
> >> > network. There is also pkgng which is a
> feature rich
> >> > replacement tool
> >> > for pkg_install available in the ports tree
> under
> >> > ports/ports-mgmt/pkg.
> >> > Packages for pkgng are available on
> pkg.FreeBSD.org.
> >> >
> >> > To use pkg.FreeBSD.org at least pkgng 1.0 RC6
> is needed
> >> and
> >> > can be
> >> > enabled in pkg.conf like this (where ${ABI}
> is
> >> dependent on
> >> > your
> >> > system):
> >> > PACKAGESITE
> : http://pkg.freebsd.org/${ABI}/latest
> >> > SRV_MIRRORS
> : YES
> >> >
> >> > With pkgng 1.0 SRV_MIRRORS is enabled by
> default and
> >> no
> >> > longer needs
> >> > to be set explicitly. If pkgng prior to 1.0
> RC6 is
> >> used
> >> > http://pkgbeta.FreeBSD.org can be used as
> packagesite
> >> > instead.
> >> >
> >> > Please keep im mind that the pkgng
> infrastructure is
> >> still
> >> > considered
> >> > as beta. More information about pkgng can be
> found at
> >> > http://wiki.FreeBSD.org/pkgng and https://github.com/pkgng/pkgng.
> >> >
> >> > Beat, on behalf of portmgr@
> >> >
> >> > [1] http://www.FreeBSD.org/doc/handbook/updating-upgrading-portsnap.html
> >> > [2] http://www.FreeBSD.org/doc/handbook/mirrors-svn.html
> >> > [3]
> >> > http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html
> >> >
> ___
> >> > freebsd-ports@freebsd.org
> >> > mailing list
> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> >> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> >> >
> >> [1] Should not this go in UPDATING now for persons
> who have
> >> it
> >> set in cron and do not read this list? Thus
> they would
> >> have time
> >> to prepare adequately or to ask questions at the
> minimum.
> >>
> >> [2] Any URL of sites which would be portsnap or svn
> updated,
> >> yet
> >> export via a cvs server for persons to continue
> using
> >> csup/cvsup?
> >>
> >> I had a random thought that this change could be
> delayed one
> >> release
> >> so that csup could depend upon a new .so. "on
> purpose" in
> >> v10 that
> >> would notify the user somehow that it is deprecated
> in
> >> v11... but
> >> that neglects cvsup...
> >>
> >> J. Bouquet
> >> ___
> >> freebsd-ports@freebsd.org
> >> mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> >> To unsubscribe, se
Re: [HEADS-UP] Announcing the end of port CVS
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 _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email & vCards X www: http://www.gid0.org- against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS-UP] Announcing the end of port CVS
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 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 Subversion to CVS
>> exporter
>> > is
>> > in place which has some limitations. For CVSup
>> mirroring
>> > cvsup
>> > based on Ezm3 is used which breaks regularly especially
>> on
>> > amd64
>> > and with Clang and becomes more and more
>> unmaintainable.
>> >
>> > For those reasons by February 28th 2013 the FreeBSD
>> ports
>> > tree will
>> > no longer be exported to CVS. Therefore ports tree
>> updates
>> > via CVS
>> > or CVSup will no longer available after that date. All
>> users
>> > who use
>> > CVS or CVSup to update the ports tree are encouraged
>> to
>> > switch to
>> > portsnap(8) [1] or for users which need more control
>> over
>> > their ports
>> > collection checkout use Subversion directly:
>> >
>> > % svn co https://svn0.us-west.FreeBSD.org/ports/head /usr/ports
>> >
>> > and update a checked out repository using:
>> >
>> > % cd /usr/ports && svn update
>> >
>> > Advanced users, or larger sites, might consider setting
>> up a
>> > local
>> > svn mirror. Both for people doing direct checkouts and
>> for
>> > people
>> > wanting to use a local mirror, they can access one of
>> the
>> > public
>> > subversion servers [2].
>> >
>> > How to set up a Subversion mirror using svnsync(1) is
>> > described in
>> > the FreeBSD Committers Guide [3]. Initial seeds to set
>> up a
>> > svnsync
>> > mirror are provided on the FreeBSD FTP mirror sites
>> under
>> > /pub/FreeBSD/development/subversion/.
>> >
>> > Binary packages for pkg_install are still provided via
>> the
>> > FTP mirror
>> > network. There is also pkgng which is a feature rich
>> > replacement tool
>> > for pkg_install available in the ports tree under
>> > ports/ports-mgmt/pkg.
>> > Packages for pkgng are available on pkg.FreeBSD.org.
>> >
>> > To use pkg.FreeBSD.org at least pkgng 1.0 RC6 is needed
>> and
>> > can be
>> > enabled in pkg.conf like this (where ${ABI} is
>> dependent on
>> > your
>> > system):
>> > PACKAGESITE : http://pkg.freebsd.org/${ABI}/latest
>> > SRV_MIRRORS : YES
>> >
>> > With pkgng 1.0 SRV_MIRRORS is enabled by default and
>> no
>> > longer needs
>> > to be set explicitly. If pkgng prior to 1.0 RC6 is
>> used
>> > http://pkgbeta.FreeBSD.org can be used as packagesite
>> > instead.
>> >
>> > Please keep im mind that the pkgng infrastructure is
>> still
>> > considered
>> > as beta. More information about pkgng can be found at
>> > http://wiki.FreeBSD.org/pkgng and https://github.com/pkgng/pkgng.
>> >
>> > Beat, on behalf of portmgr@
>> >
>> > [1] http://www.FreeBSD.org/doc/handbook/updating-upgrading-portsnap.html
>> > [2] http://www.FreeBSD.org/doc/handbook/mirrors-svn.html
>> > [3]
>> > http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html
>> > ___
>> > freebsd-ports@freebsd.org
>> > mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>> >
>> [1] Should not this go in UPDATING now for persons who have
>> it
>> set in cron and do not read this list? Thus they would
>> have time
>> to prepare adequately or to ask questions at the minimum.
>>
>> [2] Any URL of sites which would be portsnap or svn updated,
>> yet
>> export via a cvs server for persons to continue using
>> csup/cvsup?
>>
>> I had a random thought that this change could be delayed one
>> release
>> so that csup could depend upon a new .so. "on purpose" in
>> v10 that
>> would notify the user somehow that it is deprecated in
>> v11... but
>> that neglects cvsup...
>>
>> J. Bouquet
>> ___
>> freebsd-ports@freebsd.org
>> mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>>
>
> As an example of a problem they may encounter, I am stuck at
> crafting a solution (a .svn or portsnap ports tree, which I
> understand may not allow (at least without specific
> commands to "version" them...) local log files, local
> Makefile.local, etc...)
You don't understand correctly. You've been told it's fine before; svn
ignores any files it doesn't know about.
> And a ports tree which includes many
> of the latter.
>
> It seems it would be somewhat of a three-way merge
> which at many points would be not adequately scripted, since
> co
Re: Clang as default compiler November 4th
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 to see the complete list. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS-UP] Announcing the end of port CVS
--- 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
> > 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 Subversion to CVS
> exporter
> > is
> > in place which has some limitations. For CVSup
> mirroring
> > cvsup
> > based on Ezm3 is used which breaks regularly especially
> on
> > amd64
> > and with Clang and becomes more and more
> unmaintainable.
> >
> > For those reasons by February 28th 2013 the FreeBSD
> ports
> > tree will
> > no longer be exported to CVS. Therefore ports tree
> updates
> > via CVS
> > or CVSup will no longer available after that date. All
> users
> > who use
> > CVS or CVSup to update the ports tree are encouraged
> to
> > switch to
> > portsnap(8) [1] or for users which need more control
> over
> > their ports
> > collection checkout use Subversion directly:
> >
> > % svn co https://svn0.us-west.FreeBSD.org/ports/head /usr/ports
> >
> > and update a checked out repository using:
> >
> > % cd /usr/ports && svn update
> >
> > Advanced users, or larger sites, might consider setting
> up a
> > local
> > svn mirror. Both for people doing direct checkouts and
> for
> > people
> > wanting to use a local mirror, they can access one of
> the
> > public
> > subversion servers [2].
> >
> > How to set up a Subversion mirror using svnsync(1) is
> > described in
> > the FreeBSD Committers Guide [3]. Initial seeds to set
> up a
> > svnsync
> > mirror are provided on the FreeBSD FTP mirror sites
> under
> > /pub/FreeBSD/development/subversion/.
> >
> > Binary packages for pkg_install are still provided via
> the
> > FTP mirror
> > network. There is also pkgng which is a feature rich
> > replacement tool
> > for pkg_install available in the ports tree under
> > ports/ports-mgmt/pkg.
> > Packages for pkgng are available on pkg.FreeBSD.org.
> >
> > To use pkg.FreeBSD.org at least pkgng 1.0 RC6 is needed
> and
> > can be
> > enabled in pkg.conf like this (where ${ABI} is
> dependent on
> > your
> > system):
> > PACKAGESITE : http://pkg.freebsd.org/${ABI}/latest
> > SRV_MIRRORS : YES
> >
> > With pkgng 1.0 SRV_MIRRORS is enabled by default and
> no
> > longer needs
> > to be set explicitly. If pkgng prior to 1.0 RC6 is
> used
> > http://pkgbeta.FreeBSD.org can be used as packagesite
> > instead.
> >
> > Please keep im mind that the pkgng infrastructure is
> still
> > considered
> > as beta. More information about pkgng can be found at
> > http://wiki.FreeBSD.org/pkgng and https://github.com/pkgng/pkgng.
> >
> > Beat, on behalf of portmgr@
> >
> > [1] http://www.FreeBSD.org/doc/handbook/updating-upgrading-portsnap.html
> > [2] http://www.FreeBSD.org/doc/handbook/mirrors-svn.html
> > [3]
> > http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html
> > ___
> > freebsd-ports@freebsd.org
> > mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> >
> [1] Should not this go in UPDATING now for persons who have
> it
> set in cron and do not read this list? Thus they would
> have time
> to prepare adequately or to ask questions at the minimum.
>
> [2] Any URL of sites which would be portsnap or svn updated,
> yet
> export via a cvs server for persons to continue using
> csup/cvsup?
>
> I had a random thought that this change could be delayed one
> release
> so that csup could depend upon a new .so. "on purpose" in
> v10 that
> would notify the user somehow that it is deprecated in
> v11... but
> that neglects cvsup...
>
> J. Bouquet
> ___
> freebsd-ports@freebsd.org
> mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
As an example of a problem they may encounter, I am stuck at
crafting a solution (a .svn or portsnap ports tree, which I
understand may not allow (at least without specific
commands to "version" them...) local log files, local
Makefile.local, etc...)
And a ports tree which includes many
of the latter.
It seems it would be somewhat of a three-way merge
which at many points would be not adequately scripted, since
copies from the newer (.svn, portsnap) may not be adequately mirrored to the
more-files-included (as above) "final working ports tree", etc, unless it
specifically copied/gcp'd/rsync'd different types of directories
within the tree (find -depth, /files/, /src/, etc etc...) so as
to remove as well as add files
Re: [HEADS-UP] Announcing the end of port CVS
--- 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 Subversion to CVS exporter
> is
> in place which has some limitations. For CVSup mirroring
> cvsup
> based on Ezm3 is used which breaks regularly especially on
> amd64
> and with Clang and becomes more and more unmaintainable.
>
> For those reasons by February 28th 2013 the FreeBSD ports
> tree will
> no longer be exported to CVS. Therefore ports tree updates
> via CVS
> or CVSup will no longer available after that date. All users
> who use
> CVS or CVSup to update the ports tree are encouraged to
> switch to
> portsnap(8) [1] or for users which need more control over
> their ports
> collection checkout use Subversion directly:
>
> % svn co https://svn0.us-west.FreeBSD.org/ports/head /usr/ports
>
> and update a checked out repository using:
>
> % cd /usr/ports && svn update
>
> Advanced users, or larger sites, might consider setting up a
> local
> svn mirror. Both for people doing direct checkouts and for
> people
> wanting to use a local mirror, they can access one of the
> public
> subversion servers [2].
>
> How to set up a Subversion mirror using svnsync(1) is
> described in
> the FreeBSD Committers Guide [3]. Initial seeds to set up a
> svnsync
> mirror are provided on the FreeBSD FTP mirror sites under
> /pub/FreeBSD/development/subversion/.
>
> Binary packages for pkg_install are still provided via the
> FTP mirror
> network. There is also pkgng which is a feature rich
> replacement tool
> for pkg_install available in the ports tree under
> ports/ports-mgmt/pkg.
> Packages for pkgng are available on pkg.FreeBSD.org.
>
> To use pkg.FreeBSD.org at least pkgng 1.0 RC6 is needed and
> can be
> enabled in pkg.conf like this (where ${ABI} is dependent on
> your
> system):
> PACKAGESITE : http://pkg.freebsd.org/${ABI}/latest
> SRV_MIRRORS : YES
>
> With pkgng 1.0 SRV_MIRRORS is enabled by default and no
> longer needs
> to be set explicitly. If pkgng prior to 1.0 RC6 is used
> http://pkgbeta.FreeBSD.org can be used as packagesite
> instead.
>
> Please keep im mind that the pkgng infrastructure is still
> considered
> as beta. More information about pkgng can be found at
> http://wiki.FreeBSD.org/pkgng and https://github.com/pkgng/pkgng.
>
> Beat, on behalf of portmgr@
>
> [1] http://www.FreeBSD.org/doc/handbook/updating-upgrading-portsnap.html
> [2] http://www.FreeBSD.org/doc/handbook/mirrors-svn.html
> [3]
> http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html
> ___
> freebsd-ports@freebsd.org
> mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
[1] Should not this go in UPDATING now for persons who have it
set in cron and do not read this list? Thus they would have time
to prepare adequately or to ask questions at the minimum.
[2] Any URL of sites which would be portsnap or svn updated, yet
export via a cvs server for persons to continue using csup/cvsup?
I had a random thought that this change could be delayed one release
so that csup could depend upon a new .so. "on purpose" in v10 that
would notify the user somehow that it is deprecated in v11... but
that neglects cvsup...
J. Bouquet
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clang as default compiler November 4th
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-representation. > > Adding the requirement "your ports must work on clang" is adding an > ex-post-facto requirement. This creates the following matrix of what > we are implicitly asking maintainers to do: > > (FreeBSD 7|8|9|10) * (amd64|arm|i386|powerpc|sparc64) * (base gcc|base clang) > > It is completely insane to expect anyone to be able to test in all of those > environments, or even a tiny subset of them. This isn't what most people > sign up for when they sign up to maintain ports. No, I didn't mean it that way. I only meant that the people / maintainers running CURRENT will actually see that their ports don't work and if they want to keep on using them on CURRENT they need to fix them. e.g. two of the ports I maintain don't build with CLANG, yet. I just checked that on the wiki page [1]. I had to look that up manually, but would have experienced that if I my CURRENT box was building with CLANG by default. :) It's clear that we cannot expect our maintainers to check all possible combinations of FreeBSD, architecture and compiler. > > > Those who don't run CURRENT won't notice, but those who do will have to > > get their butts up and fix the ports > > I think it's foolish to assume that maintainres don't have their butts in > gear as it is. Please note, we have nearly 1300 PRs, hundreds of ports with > build errors and/or PRs, and hundreds that fail on -current only. I try to > advertise all these things the best I know how. Adding the hundreds that > fail on -clang only and then blaming the maintainers is simply going to be > counter-productive. [1] http://wiki.freebsd.org/PortsAndClang pgp2qfIiXlAlJ.pgp Description: PGP signature
Re: Clang as default compiler November 4th
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. Fortunately, that goal is much more easily achieved > than fixing ports to build and run with clang. (It's harder than it > sounds because there are certain key libs that define some paths > depending on what compiler they were built with, but still easier > than dealing with clang in the short term.) That is a well thought out, highly intuitive and completely doable idea. Therefore it will be ignored. It seems that the FreeBSD authors are more concerned with the licensing language of GCC than in getting a fully functioning port's compiler into the FreeBSD base system. Thank God that everyone isn't as narrow minded as that. Imagine if we all hated people simple because of their skin color or religion ... or do we? -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ It would save me a lot of time if you just gave up and went mad now. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clang as default compiler November 4th
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 > significant number of ports that don't even compile with gcc 4.2.1. How > many compilers do we expect the users to install? :) If a port doesn't compile with the default compiler in base, I expect that port to add a build dependency on the compiler that it actually does compiles with. Of course, I hope to not have 6 different compilers installed on my system, but the list of build or runtime dependencies are at the discretion of the port (maintainer). As you (I think) said, we can't force port maintainers to patch their ports to support clang. So even today, we have a significant number of ports that don't compile with the default compiler (GCC 4.2.1). Aren't they broken already, in the sense that they fail to tell me, the user, which compiler I should use? Thanks, Erik___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Postfix and SASL compilation problem
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 ===> The following configuration options are available for postfix-2.9.4,1: PCRE=on: Perl Compatible Regular Expressions SASL2=off: Cyrus SASLv2 (Simple Auth. and Sec. Layer) DOVECOT=off: Dovecot 1.x SASL authentication method DOVECOT2=on: Dovecot 2.x SASL authentication method SASLKRB5=off: If your SASL req. Kerberos5, select this SASLKMIT=off: If your SASL req. MIT Kerberos5, select this TLS=on: Enable SSL and TLS support BDB=on: Berkeley DB (uses WITH_BDB_VER) MYSQL=off: MySQL maps (uses WITH_MYSQL_VER) PGSQL=off: PostgreSQL maps (uses DEFAULT_PGSQL_VER) SQLITE=on: SQLite maps OPENLDAP=on: OpenLDAP maps (uses WITH_OPENLDAP_VER) LDAP_SASL=on: Enable OpenLDAP client-to-server SASL auth CDB=off: CDB maps lookups NIS=off: NIS maps lookups VDA=on: VDA (Virtual Delivery Agent 32Bit) TEST=off: SMTP/LMTP test server and generator SPF=on: SPF support (via libspf2 1.2.x) INST_BASE=off: Install into /usr and /etc/postfix ===> Use 'make config' to modify these settings Line 232 in postfix-2.9.4/src/global/dict_ldap.c doesn't contain proper path to sasl.h header file on FreeBSD. Fixed line should look like this: #include Here is the patch: ### --- dict_ldap.c.old 2012-09-11 00:39:40.0 +0200 +++ dict_ldap.c 2012-09-11 00:22:56.0 +0200 @@ -229,7 +229,7 @@ /* * SASL headers, for sasl_interact_t. Either SASL v1 or v2 should be fine. */ -#include +#include #endif ### Kindly regards, Jan Sebosik ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Need Your Office Space To Work Harder?
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, Deskcentre is here to help. We offer a Complimentary Design Consultation to help make the most of the space you have through intelligent spacial design, innovative storage solutions and affordable office furniture. We can also work with you on any projects that may require a dedicated office design and installation service. Our services can work hand in hand with yours, to offer an unrivalled customer experience. Complimentary Design Service to help make the most of your spaceExpert team to plan, design and build a functional, yet stylish environment for youSee your office brought to life through 2D designs and 3D walkthroughs Affordable solutions to truly maximise your budgetOver 10,000 practical and affordable furniture and accessory solutions to choose from online at www.deskcentre.co.ukOver 25 years trusted expertise in creating functional and stylish office solutions Great Prices On Furniture and Office Solutions Stunning Boardroom Table 2700mm x 1200mm x 740mm high Silver frame on wrap around leg, other frame finishes available POA Choice of coloured tops available, special colours POA Built in LED lighting system to give the WOW factor 5 year warranty PRICE INCLUDES DELIVERY & INSTALLATION Was £3,345, now only £1,339 In built cable management 12mm Toughened black glass top panel Silver frame with cable risers Horizontal cable ducts along the beams Cable ducts will also accept power & data modules Leg frames are die cast Warranty 5 years PRICE INCLUDES DELIVERY & INSTALLATION Was £730, now only £365 Executive Black Leather chair with chrome frame Soft pad for extra comfort Gas Lift height adjustment High quality Leather upholstery Superior construction 5 star Chrome swivel base with chrome hooded twin wheel castors 2 year Warranty PRICE INCLUDES DELIVERY Only £325 Save today at www.deskcentre.co.uk [http://www.deskcentre.co.uk/making-office-spaces-work-harder/], or call 0845 313 7456 *Terms and conditions apply. For full details click here [http://shop.deskcentre.co.uk/terms-and-conditions.html] Click here to unsubscribe http://oomph.digitalwelly.com/t/r-u-kyjkjyk-yktdlhdtyh-m/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clang as default compiler November 4th
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 requirement "your ports must work on clang" is adding an > ex-post-facto requirement. This creates the following matrix of what > we are implicitly asking maintainers to do: > > (FreeBSD 7|8|9|10) * (amd64|arm|i386|powerpc|sparc64) * (base gcc|base clang) > > It is completely insane to expect anyone to be able to test in all of those > environments, or even a tiny subset of them. This isn't what most people > sign up for when they sign up to maintain ports. > >> Those who don't run CURRENT won't notice, but those who do will have to >> get their butts up and fix the ports > > I think it's foolish to assume that maintainres don't have their butts in > gear as it is. Please note, we have nearly 1300 PRs, hundreds of ports with > build errors and/or PRs, and hundreds that fail on -current only. I try to > advertise all these things the best I know how. Adding the hundreds that > fail on -clang only and then blaming the maintainers is simply going to be > counter-productive. Write the day on your calendars folks, I completely agree with what Mark said above. :) This is a big part of what I meant with some of my more colorful comments in my original post on this topic. Doug ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clang as default compiler November 4th
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 with gcc 4.2.1. How many compilers do we expect the users to install? :) 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 is much more easily achieved than fixing ports to build and run with clang. (It's harder than it sounds because there are certain key libs that define some paths depending on what compiler they were built with, but still easier than dealing with clang in the short term.) Once that is done, the compiler in the base is an afterthought, and we can do away with gcc in the base altogether much more easily. Users who want to help support building ports with clang can continue to do so. Doug ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clang as default compiler November 4th
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. > > Adding the requirement "your ports must work on clang" is adding an > ex-post-facto requirement. This creates the following matrix of what > we are implicitly asking maintainers to do: > > (FreeBSD 7|8|9|10) * (amd64|arm|i386|powerpc|sparc64) * (base gcc|base clang) > > It is completely insane to expect anyone to be able to test in all of those > environments, or even a tiny subset of them. This isn't what most people > sign up for when they sign up to maintain ports. > >> Those who don't run CURRENT won't notice, but those who do will have to >> get their butts up and fix the ports > > I think it's foolish to assume that maintainres don't have their butts in > gear as it is. Please note, we have nearly 1300 PRs, hundreds of ports with > build errors and/or PRs, and hundreds that fail on -current only. I try to > advertise all these things the best I know how. Adding the hundreds that > fail on -clang only and then blaming the maintainers is simply going to be > counter-productive. I'd also guess that FreeBSD ports is probably the biggest exposure clang has ever seen to 3rd party code. I can't think of any other project except maybe macports who try to run clang over some much 3rd party code and so FreeBSD ports is hitting all the bumps in the road that most people get to ignore. - Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Clang as default compiler November 4th
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 an ex-post-facto requirement. This creates the following matrix of what we are implicitly asking maintainers to do: (FreeBSD 7|8|9|10) * (amd64|arm|i386|powerpc|sparc64) * (base gcc|base clang) It is completely insane to expect anyone to be able to test in all of those environments, or even a tiny subset of them. This isn't what most people sign up for when they sign up to maintain ports. > Those who don't run CURRENT won't notice, but those who do will have to > get their butts up and fix the ports I think it's foolish to assume that maintainres don't have their butts in gear as it is. Please note, we have nearly 1300 PRs, hundreds of ports with build errors and/or PRs, and hundreds that fail on -current only. I try to advertise all these things the best I know how. Adding the hundreds that fail on -clang only and then blaming the maintainers is simply going to be counter-productive. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11-toolkits/swt
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 in the old version off of my daily periodic. >> >> Meanwhile, I've had success with x11-toolkits/swt-devel for >> mail/davmail and java/eclipse (btw, for me eclipse compiles only if >> swt-devel is installed, not swt). >> > > I think we can safely replace x11-toolkits/swt with x11-toolkits/swt-devel. As long as davmail continues to work, I'm happy. :) Does anyone have patches? I'm happy to test it this weekend. Doug ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
