On Thu, 7 Aug 2003, Riku Voipio wrote:
> Sounds really odd. Maybe the previous gcc binaries you had where
> corrupted during your previous hardaware problems. I once got some
> really funky errors after running fsck on /usr with buggy ram.
>
I thought of that but fsck and badblocks both reported
On Wed, Aug 06, 2003 at 11:18:18PM -0400, Jaldhar H. Vyas wrote:
> On Tue, 5 Aug 2003, Jaldhar H. Vyas wrote:
> > Could someone please NMU dovecot adding the patch in bug #203892?
> > Either gcc 3.3.1 sucks or I'm having another hardware problem,
> In case anyone care
On Tue, 5 Aug 2003, Jaldhar H. Vyas wrote:
> Could someone please NMU dovecot adding the patch in bug #203892?
>
> Either gcc 3.3.1 sucks or I'm having another hardware problem,
>
> ...
>
> Making all in lib
> make[4]: Entering directory
> `/home/jaldhar/src
Could someone please NMU dovecot adding the patch in bug #203892?
Either gcc 3.3.1 sucks or I'm having another hardware problem,
...
Making all in lib
make[4]: Entering directory
`/home/jaldhar/src/dovecot/dovecot-0.99.10/src/lib'
i386-linux-gcc -DHAVE_CONFIG_H -I. -I. -I../.. -g
4 matches
Mail list logo