On Jun 14, 2005, at 1:01 AM, Matthew Sachs wrote:
And that's why someone (possibly me, ideally someone with more
hardware to spare) should do runs against FSF mainline.
One thing to watch out is the APPLE LOCAL patches in back-end/code
gen area, particularly related to alignment and other
On Jun 13, 2005, at 19:49, Andrew Pinski wrote:
On Jun 13, 2005, at 10:36 PM, Matthew Sachs wrote:
I've been doing regular builds of Fink against Apple's branch,
building our last release alongside our latest engineering build
and comparing the two. See:
http://cvs.sourceforge.net/vie
Scott Robert Ladd wrote:
Given the recent problems with the 4.0.0 release and major packages like
KDE and the kernel, has anyone considered testing releases by completely
compiling a Linux system?
I'm all for more testing -- but I have a standard rant about it being
easier to run tests than to
On Jun 13, 2005, at 10:36 PM, Matthew Sachs wrote:
I've been doing regular builds of Fink against Apple's branch,
building our last release alongside our latest engineering build and
comparing the two. See:
http://cvs.sourceforge.net/viewcvs.py/fink/scripts/buildfink/
http://fink.ope
I've been doing regular builds of Fink against Apple's branch,
building our last release alongside our latest engineering build and
comparing the two. See:
http://cvs.sourceforge.net/viewcvs.py/fink/scripts/buildfink/
http://fink.opendarwin.org/build/2005-05-08/out/report.html
On Jun 12, 2005, at 10:51 AM, Gerald Pfeifer wrote:
Note, though, that this is only one part of the equation. A most
significant amount of work also goes into analysing and potentially
fixing packages which do not compile any longer and submit fixes
upstream.
:-( Sometimes we wish that gcc ha
Gerald Pfeifer wrote:
> Are you sure nobody is doing this? Or to phrase it differently: have
> you checked Bugzilla and the ChangeLogs as to what kind of reports and
> patches SUSE and Red Hat have contributed to GCC 4.0 in recent months
> and weeks? :-)
My suggestion stems from the code-generati
Hi,
On Sunday 12 June 2005 19:51, Gerald Pfeifer wrote:
> > Given the recent problems with the 4.0.0 release and major packages like
> > KDE and the kernel, has anyone considered testing releases by completely
> > compiling a Linux system?
> > I'm willing to implement this, if it's deemed useful
On Thu, 9 Jun 2005, Scott Robert Ladd wrote:
> Given the recent problems with the 4.0.0 release and major packages like
> KDE and the kernel, has anyone considered testing releases by completely
> compiling a Linux system?
Are you sure nobody is doing this? Or to phrase it differently: have
you c
Scott Robert Ladd wrote:
Joe Buck wrote:
With 4.0.0, compiling a complete GNU/Linux distribution reveals bugs
in GCC, but even more bugs in C++ software that is not valid C++.
Assuming we can get the distros to fix the latter set of problems...
I don't have a good solution for this problem, ot
Joe Buck wrote:
> With 4.0.0, compiling a complete GNU/Linux distribution reveals bugs
> in GCC, but even more bugs in C++ software that is not valid C++.
> Assuming we can get the distros to fix the latter set of problems...
I don't have a good solution for this problem, other than education.
>
Arthur Nascimento wrote:
>>Given the recent problems with the 4.0.0 release and major packages like
>>KDE and the kernel, has anyone considered testing releases by completely
>>compiling a Linux system?
> Yes, people do it all the time. Check Sourcemage, LFS and DIY:
>
> http://www.sourcemage.org
2005/6/9, Scott Robert Ladd <[EMAIL PROTECTED]>:
> Given the recent problems with the 4.0.0 release and major packages like
> KDE and the kernel, has anyone considered testing releases by completely
> compiling a Linux system?
Yes, people do it all the time. Check Sourcemage, LFS and DIY:
http://
On Thu, Jun 09, 2005 at 04:42:33PM -0400, Scott Robert Ladd wrote:
> Given the recent problems with the 4.0.0 release and major packages like
> KDE and the kernel, has anyone considered testing releases by completely
> compiling a Linux system?
With 4.0.0, compiling a complete GNU/Linux distributi
Scott wrote:
> Given the recent problems with the 4.0.0 release and major packages like
> KDE and the kernel, has anyone considered testing releases by completely
> compiling a Linux system?
It's kind of hard to do for a new major release,
since the apps and kernel might not be ported yet,
but 4.
15 matches
Mail list logo
