On Tue, Dec 15, 1998 at 08:57:47PM +, [EMAIL PROTECTED] wrote:
> Have there been duplicates? I suppose that you first need to move your
> mailfile /var/spool/mail/my_account to your $HOME and then start
> formail/procmail as procmail appends the mails while cat reads them again
> and again?!
Have there been duplicates? I suppose that you first need to move your
mailfile /var/spool/mail/my_account to your $HOME and then start
formail/procmail as procmail appends the mails while cat reads them again
and again?!
Alex.
On Tue, 15 Dec 1998, Shao Zhang wrote:
> Hi all,
> I a
Hi all,
I am very confused. please help. I am trying to filt my current
mail to different folders.
In pine, I have about 200 old mails...
so I did
cat /var/spool/mail/my_account | formail -s procmail.
All of sudden, it filts out over 5000 thousands
Hello,
> >I left the source as it was, but added some softlinks, like
> >/usr/include/X11/GL -> /usr/include/GL
>
> Me to, but I had to edit out some refs. to a /GL/GLw/ directory included
> file - the header file was actually under /GL, and Glw doesn't exist on
> my system.
I used softlinks thr
>Subject: Re: g++2.8, egcs, gcc 2.7.2, etc. - *very confused*
>To: [EMAIL PROTECTED] (Martin Waller)
>Date: Tue, 8 Dec 1998 16:30:50 +1100 (EST)
>Cc: debian-user@lists.debian.org
>From: Jiri Baum <[EMAIL PROTECTED]>
>
>Hello,
>
>> Over the weekend, I downlao
On Wed, Dec 09, 1998 at 00:13:16 -0500, Ed Cogburn wrote:
> > >Read /usr/doc/gcc/README.Debian .
> It didn't say *why* we have an apparent fork in compiler development.
It doesn't contain a full history of the free software movement either, as
that's out of scope for that document too.
> Since t
Martin Waller wrote:
>
> >
> >Read /usr/doc/gcc/README.Debian .
> >
>
> I did but was still confused :(
>
>
It didn't say *why* we have an apparent fork in compiler development.
Since the gcc compiler is at the core of Linux (behind only the kernel
itself in importance), having a semi-
Hello,
> Over the weekend, I downlaoded V 1.20 onto /usr/local/.
Did the same last night.
> I tried compiling it and after finding out that I needed all the OpenGl
> stuff and isntalling that to (V. annoying by the way - had even to edit some
> of the source code to get rid of those probelms)
>
>Read /usr/doc/gcc/README.Debian .
>
I did but was still confused :(
>> Being naive enough to try anything, and having heard of all sorts of
>> problems with egcs and g++, I decided to scrap g++2.8 and put
g++2.7.2 on.
>> (I had egcs 2.90.29, dated 19980515).
>
>g++2.7.2 is intended only for
On Mon, Dec 07, 1998 at 01:50:48 -0800, Martin Waller wrote:
> I am stunningly confused about the whole c and c++ suite thing that's
> going on (I'm still in HAMM - it's *not * the __register_frame_info
> stuff!).
Read /usr/doc/gcc/README.Debian .
> Being naive enough to try anything, and havin
Hi,
I am stunningly confused about the whole c and c++ suite thing that's
going on (I'm still in HAMM - it's *not * the __register_frame_info
stuff!).
Here's my story and a plea for a clear explanation of what's what and
what I need to compile kernels, c++ toolkits and stuff.
Over the weekend
11 matches
Mail list logo