Re: Any objections to swapping base compilers to make gcc4.7 the default?

[Justin Sherrill <justin@xxxxxxxxxxxxxxxxxx>]

--f46d043891bd6ae73004d4ac68fa
Content-Type: text/plain; charset=ISO-8859-1

Sounds like there wouldn't be any noticeable/unfixable effect, then.

It's always easy to agree with something when I'm not doing the actual
work, of course.


On Fri, Feb 1, 2013 at 11:03 AM, John Marino <dragonflybsd@marino.st> wrote:

> So
> 1) They are broken permanently until A) somebody patches them or B)
> somebody updates the package which has a good chance of working with gcc47
> 2) They aren't broken if you use DRAGONFLY_CCVER=gcc44 which we have done
> in the pkg themselves for those pkgs hopelessly broken on gcc4.7. The ones
> that can be patches do not feature this.  That shouldn't stop people from
> using DRAGONFLY_CCVER on packages known to previously build.  It's a
> legitimate technique.
> 3) this is the latest excerpt bulk build (follows)
> The gnustep-base is a separate multiplatform-disaster.  The rest of the
> failures are leaf packages.  Nothing too major.  Building with gcc44
> probably gets you another 100 packages I would think, at most.
>
> pkgsrc bulk build report
> ========================
>
> DragonFly 3.3/i386
> Compiler: gcc
>
> Build start: 2013-01-26 00:26
> Build end:   2013-01-30 20:15
>
> Total number of packages:      12037
>   Successfully built:          11152
>   Failed to build:               149
>   Depending on failed package:    72
>   Explicitly broken or masked:   598
>   Depending on masked package:    66
>
> Packages breaking the most other packages
>
> Package                               Breaks Maintainer
> ------------------------------**------------------------------**
> -------------
> devel/gnustep-base                        22 rh@NetBSD.org
> graphics/opencv                            6 anthony.mallet@laas.fr
> parallel/mpi-ch                            5 asau@inbox.ru
> textproc/cabocha                           5 obache@NetBSD.org
> emulators/qemu                             4 pkgsrc-users@NetBSD.org
> graphics/kdegraphics3                      3 pkgsrc-users@NetBSD.org
> devel/ruby-thrift                          3 tonnerre@NetBSD.org
> devel/xulrunner10                          3 tnn@NetBSD.org
> emulators/wine-devel                       3 adam@NetBSD.org
> games/plib                                 3 rh@NetBSD.org
>
>
>
>
> On 2/1/2013 16:40, Justin Sherrill wrote:
>
>> The only thing I can think of: can you quantify which packages aren't
>> building?  It sounds like this will break some packages, at least
>> temporarily, but I don't know which.
>>
>> The ideal scenario is to never have anyone need to/care to put
>> DRAGONFLY_CCVER into their mk.conf.  That might be likely if the
>> packages affected are old enough/rarely used enough.
>>
>

--f46d043891bd6ae73004d4ac68fa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sounds like there wouldn&#39;t be any noticeable/unfixable=
 effect, then. =A0<div><br></div><div style>It&#39;s always easy to agree w=
ith something when I&#39;m not doing the actual work, of course.</div></div=
>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Feb 1=
, 2013 at 11:03 AM, John Marino <span dir=3D"ltr">&lt;<a href=3D"mailto:dra=
gonflybsd@marino.st" target=3D"_blank">dragonflybsd@marino.st</a>&gt;</span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">So<br>
1) They are broken permanently until A) somebody patches them or B) somebod=
y updates the package which has a good chance of working with gcc47<br>
2) They aren&#39;t broken if you use DRAGONFLY_CCVER=3Dgcc44 which we have =
done in the pkg themselves for those pkgs hopelessly broken on gcc4.7. The =
ones that can be patches do not feature this. =A0That shouldn&#39;t stop pe=
ople from using DRAGONFLY_CCVER on packages known to previously build. =A0I=
t&#39;s a legitimate technique.<br>

3) this is the latest excerpt bulk build (follows)<br>
The gnustep-base is a separate multiplatform-disaster. =A0The rest of the f=
ailures are leaf packages. =A0Nothing too major. =A0Building with gcc44 pro=
bably gets you another 100 packages I would think, at most.<br>
<br>
pkgsrc bulk build report<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
>
<br>
DragonFly 3.3/i386<br>
Compiler: gcc<br>
<br>
Build start: 2013-01-26 00:26<br>
Build end: =A0 2013-01-30 20:15<br>
<br>
Total number of packages: =A0 =A0 =A012037<br>
=A0 Successfully built: =A0 =A0 =A0 =A0 =A011152<br>
=A0 Failed to build: =A0 =A0 =A0 =A0 =A0 =A0 =A0 149<br>
=A0 Depending on failed package: =A0 =A072<br>
=A0 Explicitly broken or masked: =A0 598<br>
=A0 Depending on masked package: =A0 =A066<br>
<br>
Packages breaking the most other packages<br>
<br>
Package =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Breaks =
Maintainer<br>
------------------------------<u></u>------------------------------<u></u>-=
------------<br>
devel/gnustep-base =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A022 rh@Net=
BSD.org<br>
graphics/opencv =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A06 <a=
 href=3D"mailto:anthony.mallet@laas.fr"; target=3D"_blank">anthony.mallet@la=
as.fr</a><br>
parallel/mpi-ch =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A05 <a=
 href=3D"mailto:asau@inbox.ru"; target=3D"_blank">asau@inbox.ru</a><br>
textproc/cabocha =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 5 obac=
he@NetBSD.org<br>
emulators/qemu =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4 pk=
gsrc-users@NetBSD.org<br>
graphics/kdegraphics3 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A03 pkgsrc-u=
sers@NetBSD.org<br>
devel/ruby-thrift =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A03 tonn=
erre@NetBSD.org<br>
devel/xulrunner10 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A03 tnn@=
NetBSD.org<br>
emulators/wine-devel =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 3 adam@Net=
BSD.org<br>
games/plib =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
3 rh@NetBSD.org<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
<br>
On 2/1/2013 16:40, Justin Sherrill wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The only thing I can think of: can you quantify which packages aren&#39;t<b=
r>
building? =A0It sounds like this will break some packages, at least<br>
temporarily, but I don&#39;t know which.<br>
<br>
The ideal scenario is to never have anyone need to/care to put<br>
DRAGONFLY_CCVER into their mk.conf. =A0That might be likely if the<br>
packages affected are old enough/rarely used enough.<br>
</blockquote>
</div></div></blockquote></div><br></div>

--f46d043891bd6ae73004d4ac68fa--