C.Schmidts
2005-10-19 07:27:01 UTC
Ich habe jetzt rausgefunden dass mein Problem mit dem IF-Statement wohl
an einem fehlerhaften Maildrop-Binary liegt......
Aber wie biege ich das wieder hin ?!?!
Hier der auszug aus der Maildrop Mailing-List.
My maildrop was not working because of a broken binary. Thank you for
your help!
- Steve
-----Original Message-----
From: Matthias Andree [mailto:***@dt.e-technik.uni-dortmund.de]
Sent: Wednesday, November 03, 2004 6:08 AM
To: Steve Quezadas
Subject: Re: [maildropl] "If" statement not working
- HTML isn"t welcome on mailing
lists (and would best be banned).
signal 4 is SIGILL, illegal instruction, which usually happens when
you"ve enabled instructions that your processor doesn"t support, for
instance using gcc -march=i686 on a Pentium (which requires i586) or
compiling for SPARCv8 and running on a v7 CPU or similar.
On some machines, it can also happen with unaligned access but this is
rather uncommonly seen in C/C++ and would usually coincide with hefty
compiler warnings about alignment.
an einem fehlerhaften Maildrop-Binary liegt......
Aber wie biege ich das wieder hin ?!?!
Hier der auszug aus der Maildrop Mailing-List.
My maildrop was not working because of a broken binary. Thank you for
your help!
- Steve
-----Original Message-----
From: Matthias Andree [mailto:***@dt.e-technik.uni-dortmund.de]
Sent: Wednesday, November 03, 2004 6:08 AM
To: Steve Quezadas
Subject: Re: [maildropl] "If" statement not working
This is weird, my simple recipe is not working because maildrop seems
tobe choking on the "if" statement. I checked google and newsgroups and
Icouldn"t find much on this.
First of all, please fix your mailer configuration according to- HTML isn"t welcome on mailing
lists (and would best be banned).
maildrop: signal 0x04
Then, recompile maildrop with proper compiler settings.signal 4 is SIGILL, illegal instruction, which usually happens when
you"ve enabled instructions that your processor doesn"t support, for
instance using gcc -march=i686 on a Pentium (which requires i586) or
compiling for SPARCv8 and running on a v7 CPU or similar.
On some machines, it can also happen with unaligned access but this is
rather uncommonly seen in C/C++ and would usually coincide with hefty
compiler warnings about alignment.
--
Matthias Andree
Matthias Andree