On Tue, Aug 03, 2004 at 10:46:30AM +0100, Paul Martin wrote:
> On Tue, Aug 03, 2004 at 09:50:03AM +0200, Wouter Verhelst wrote:
>
> > Hm. It didn't build, but that's probably because it doesn't use whatever
> > I specify as CC:
> >
> > cc -Wall -D_GNU_SOURCE -DLinux -DVERSION=\"3.7\" -Wall -g -O2
On Tue, Aug 03, 2004 at 09:50:03AM +0200, Wouter Verhelst wrote:
> Hm. It didn't build, but that's probably because it doesn't use whatever
> I specify as CC:
>
> cc -Wall -D_GNU_SOURCE -DLinux -DVERSION=\"3.7\" -Wall -g -O2
> -D_FILE_OFFSET_BITS=64 -c -o config.o config.c
> config.c: In functi
On Tue, Aug 03, 2004 at 10:25:17AM +0200, Wouter Verhelst wrote:
> On Tue, Aug 03, 2004 at 09:58:57AM +0200, Andreas Metzler wrote:
> > On 2004-08-03 Wouter Verhelst <[EMAIL PROTECTED]> wrote:
> > > On Mon, Aug 02, 2004 at 11:51:17PM +0200, Wouter Verhelst wrote:
> > [...]
> > > > I'm preparing to
On Tue, Aug 03, 2004 at 09:58:57AM +0200, Andreas Metzler wrote:
> On 2004-08-03 Wouter Verhelst <[EMAIL PROTECTED]> wrote:
> > On Mon, Aug 02, 2004 at 11:51:17PM +0200, Wouter Verhelst wrote:
> [...]
> > > I'm preparing to perform a build with gcc-3.4 on another m68k host,
> > > running unstable;
On 2004-08-03 Wouter Verhelst <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 02, 2004 at 11:51:17PM +0200, Wouter Verhelst wrote:
[...]
> > I'm preparing to perform a build with gcc-3.4 on another m68k host,
> > running unstable; I'll follow up with the results ASAP.
> Hm. It didn't build, but that's p
On Mon, Aug 02, 2004 at 11:51:17PM +0200, Wouter Verhelst wrote:
> On Mon, Aug 02, 2004 at 06:25:20PM +0100, Paul Martin wrote:
> > On Mon, Aug 02, 2004 at 01:43:00PM +0200, Jeroen van Wolffelaar wrote:
> > > gcc-3.0 isn't available in sid/sarge on m68k. Suppose that your package
> > > FTBFS's on m
On Mon, Aug 02, 2004 at 02:52:41PM -0700, Steve Langasek wrote:
> This issue warrants opening an RC bug against logrotate, that should be
> addressed before sarge. There will probably be someone on debian-68k
> (cc:ed) who can verify for us whether logrotate does build with gcc-3.4,
Actually, you
Hi Paul,
On Mon, Aug 02, 2004 at 12:25:26PM +0100, Paul Martin wrote:
> The m68k buildd was choking on logrotate due to a gcc internal error in
> gcc-3.3. I've been pestered into ensuring that 3.7 gets into sarge
> [m68k].
> All other arches are up-to-date in sarge. Only m68k has a much older
> r
On Mon, Aug 02, 2004 at 06:25:20PM +0100, Paul Martin wrote:
> On Mon, Aug 02, 2004 at 01:43:00PM +0200, Jeroen van Wolffelaar wrote:
> > gcc-3.0 isn't available in sid/sarge on m68k. Suppose that your package
> > FTBFS's on m68k in sarge (I'm not saying it does, but it could easily be
> > the case
On Mon, Aug 02, 2004 at 01:43:00PM +0200, Jeroen van Wolffelaar wrote:
> On Mon, Aug 02, 2004 at 12:25:26PM +0100, Paul Martin wrote:
> > The m68k buildd was choking on logrotate due to a gcc internal error in
> > gcc-3.3. I've been pestered into ensuring that 3.7 gets into sarge
> > [m68k].
> >
>
On Mon, Aug 02, 2004 at 12:25:26PM +0100, Paul Martin wrote:
> The m68k buildd was choking on logrotate due to a gcc internal error in
> gcc-3.3. I've been pestered into ensuring that 3.7 gets into sarge
> [m68k].
>
> All other arches are up-to-date in sarge. Only m68k has a much older
> revision,
The m68k buildd was choking on logrotate due to a gcc internal error in
gcc-3.3. I've been pestered into ensuring that 3.7 gets into sarge
[m68k].
All other arches are up-to-date in sarge. Only m68k has a much older
revision, due to the gcc error.
What I've done is to compile a binary-only upload
12 matches
Mail list logo
