On Mon, Jun 09, 2003 at 10:52:47AM +1000, Daniel Stone wrote:
> On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
> >From http://necrotic.deadbeast.net/xfree86/, I built the
> > branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
> > current debian ppc sid plus todays freet
On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
> Daniel,
>From http://necrotic.deadbeast.net/xfree86/, I built the
> branches-4.3.0-sid-debian-2003.06.07.tar.gz.
This is the best reason I've yet seen for imposing access controls on
that directory, or discontinuing this service e
On Sun, Jun 08, 2003 at 06:38:10PM -0400, Jack Howarth wrote:
> Branden,
> Well all I can say is that the current xfree86 4.3.0 branch
> debian 0pre1v1 sources that are posted build fine on debian ppc
> sid using gcc 3.3 without any evidence of this bug.
Well, you say they exhibit no "evidenc
On Mon, Jun 09, 2003 at 10:28:04AM +1000, Daniel Stone wrote:
> I'm going to see if I can shake this issue down after exams (four days),
> but it basically looks like gcc3.3 is *just* *not* *ready*. It doesn't
> build XFree86 at all on a couple of architectures, it ICEs on KDE on
> mips{,el}, it ha
On Mon, Jun 09, 2003 at 10:52:47AM +1000, Daniel Stone wrote:
> On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
> >From http://necrotic.deadbeast.net/xfree86/, I built the
> > branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
> > current debian ppc sid plus todays freet
On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
> Daniel,
>From http://necrotic.deadbeast.net/xfree86/, I built the
> branches-4.3.0-sid-debian-2003.06.07.tar.gz.
This is the best reason I've yet seen for imposing access controls on
that directory, or discontinuing this service e
On Sun, Jun 08, 2003 at 06:38:10PM -0400, Jack Howarth wrote:
> Branden,
> Well all I can say is that the current xfree86 4.3.0 branch
> debian 0pre1v1 sources that are posted build fine on debian ppc
> sid using gcc 3.3 without any evidence of this bug.
Well, you say they exhibit no "evidenc
On Mon, Jun 09, 2003 at 10:28:04AM +1000, Daniel Stone wrote:
> I'm going to see if I can shake this issue down after exams (four days),
> but it basically looks like gcc3.3 is *just* *not* *ready*. It doesn't
> build XFree86 at all on a couple of architectures, it ICEs on KDE on
> mips{,el}, it ha
On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
>From http://necrotic.deadbeast.net/xfree86/, I built the
> branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
> current debian ppc sid plus todays freetype6 2.1.4-4 package.
> The resulting xfree86 packages, when installed
Daniel,
From http://necrotic.deadbeast.net/xfree86/, I built the
branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
current debian ppc sid plus todays freetype6 2.1.4-4 package.
The resulting xfree86 packages, when installed, allow me to
telnet back into my machine and open a xcalc in
On Sun, Jun 08, 2003 at 06:38:10PM -0400, Jack Howarth wrote:
> Well all I can say is that the current xfree86 4.3.0 branch
> debian 0pre1v1 sources that are posted build fine on debian ppc
> sid using gcc 3.3 without any evidence of this bug.
a) builds != works.
b) Where did you obtain those
On Sun, Jun 08, 2003 at 05:10:50PM -0500, Branden Robinson wrote:
> On Sun, Jun 08, 2003 at 02:00:39PM -0400, Jack Howarth wrote:
> > Branden,
> >We have never seen this problem with gcc 3.3 builds of XFree86
> > 4.3.0, right?
>
> Bzzzt, stop right there.
>
> What makes you think anyone has a
On Sun, Jun 08, 2003 at 08:48:56PM -0400, Jack Howarth wrote:
>From http://necrotic.deadbeast.net/xfree86/, I built the
> branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
> current debian ppc sid plus todays freetype6 2.1.4-4 package.
> The resulting xfree86 packages, when installed
Daniel,
From http://necrotic.deadbeast.net/xfree86/, I built the
branches-4.3.0-sid-debian-2003.06.07.tar.gz. This is against
current debian ppc sid plus todays freetype6 2.1.4-4 package.
The resulting xfree86 packages, when installed, allow me to
telnet back into my machine and open a xcalc in
Branden,
Well all I can say is that the current xfree86 4.3.0 branch
debian 0pre1v1 sources that are posted build fine on debian ppc
sid using gcc 3.3 without any evidence of this bug.
Jack
On Sun, Jun 08, 2003 at 06:38:10PM -0400, Jack Howarth wrote:
> Well all I can say is that the current xfree86 4.3.0 branch
> debian 0pre1v1 sources that are posted build fine on debian ppc
> sid using gcc 3.3 without any evidence of this bug.
a) builds != works.
b) Where did you obtain those
On Sun, Jun 08, 2003 at 05:10:50PM -0500, Branden Robinson wrote:
> On Sun, Jun 08, 2003 at 02:00:39PM -0400, Jack Howarth wrote:
> > Branden,
> >We have never seen this problem with gcc 3.3 builds of XFree86
> > 4.3.0, right?
>
> Bzzzt, stop right there.
>
> What makes you think anyone has a
On Sun, Jun 08, 2003 at 02:00:39PM -0400, Jack Howarth wrote:
> Branden,
>We have never seen this problem with gcc 3.3 builds of XFree86
> 4.3.0, right?
Bzzzt, stop right there.
What makes you think anyone has any Debian XFree86 packages of 4.3.0
built with GCC 3.3? That version of the compi
Branden,
Well all I can say is that the current xfree86 4.3.0 branch
debian 0pre1v1 sources that are posted build fine on debian ppc
sid using gcc 3.3 without any evidence of this bug.
Jack
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". T
On Sun, Jun 08, 2003 at 02:00:39PM -0400, Jack Howarth wrote:
> Branden,
>We have never seen this problem with gcc 3.3 builds of XFree86
> 4.3.0, right?
Bzzzt, stop right there.
What makes you think anyone has any Debian XFree86 packages of 4.3.0
built with GCC 3.3? That version of the compi
Branden,
We have never seen this problem with gcc 3.3 builds of XFree86
4.3.0, right? It sounds like it might be better to just push
XFree86 4.3.0 into sid and shake out the remaining bugs there.
Now that freetype6 has been regressed back to a binary compatible
state are there really that many b
Branden,
We have never seen this problem with gcc 3.3 builds of XFree86
4.3.0, right? It sounds like it might be better to just push
XFree86 4.3.0 into sid and shake out the remaining bugs there.
Now that freetype6 has been regressed back to a binary compatible
state are there really that many b
On Sun, Jun 08, 2003 at 06:18:20AM -0500, Debian Bug Tracking System wrote:
> Processing commands for [EMAIL PROTECTED]:
>
> > reassign 196575 xlibs
> Bug#196575: [xlib]: gcc3.3 screws up authentication
> Bug reassigned from package `xserver-xfree86' to `xlibs'.
>
> > merge 196554 196575
> Bug#19
On Sun, Jun 08, 2003 at 06:18:20AM -0500, Debian Bug Tracking System wrote:
> Processing commands for [EMAIL PROTECTED]:
>
> > reassign 196575 xlibs
> Bug#196575: [xlib]: gcc3.3 screws up authentication
> Bug reassigned from package `xserver-xfree86' to `xlibs'.
>
> > merge 196554 196575
> Bug#19
24 matches
Mail list logo
