Wayne Pascoe wrote:
> That looks like a bit of a bug with GCC to me, but I've not looked at
> the code or the compile process yet, so I'll log a bug with the
> appropriate organisation / group once I work out what is causing this.
If I were you, I'd report the bug first. Note that it doesn't af
On 19 Apr 2007, at 13:08, Jay Lee wrote:
Forgot to mention that I've successfully built courier and courier-
authlib RPMS for RHEL5 x86_64 which should be 100% compatible with
CentOS5 also, I've your interested in them as a temporary solution
to get you up and running, let me know and I'll
Il giorno 19/apr/07, alle ore 12:30, Wayne Pascoe ha scritto:
On Thu, April 19, 2007 11:18 am, Sam Varshavchik wrote:
Compiling esmtpclient.c
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See http://bugzilla.redhat.com/bugzilla> for instructions.
Run memtest to
Wayne Pascoe wrote:
On Thu, April 19, 2007 11:18 am, Sam Varshavchik wrote:
Compiling esmtpclient.c
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See http://bugzilla.redhat.com/bugzilla> for instructions.
Run memtest to check for bad RAM.
It's a vi
On Thu, April 19, 2007 11:18 am, Sam Varshavchik wrote:
>> Compiling esmtpclient.c
>> gcc: Internal error: Killed (program cc1)
>> Please submit a full bug report.
>> See http://bugzilla.redhat.com/bugzilla> for instructions.
>
> Run memtest to check for bad RAM.
It's a virtual server running on
Wayne Pascoe writes:
Hi all,
Is there any way to build the Courier RPMs one at a time from the tarball
instead of building all of them? For example, just build imap, then just
build pop3d, etc... ?
No.
Compiling esmtpclient.c
gcc: Internal error: Killed (program cc1)
Please submit a full b
Hi all,
Is there any way to build the Courier RPMs one at a time from the tarball
instead of building all of them? For example, just build imap, then just
build pop3d, etc... ?
The reason I ask is that when I do the full build, I am getting the
following error:
--- START ERROR ---
Making all in