Those errors can occur if you include files within a C block.
For example, the following works well:
#include
int main() {}
but this fails with exactly the errors you have seen:
int main() {
#include
}
This can happen sometimes by accident, for example when you
are conditionally compiling bra
+ii myspell-en-us [myspell-dict 1:2.0.3-2English_american dictionary for my
- --
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://www.littletux.net
ICQ: 326674288
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG w
Hi,
I wanted to retry this with a more recent linux kernel.
Did you try anything specific, and which kernel did you use?
Does the debug/log output of cdrecord look similar to
the one I attached to the original posting?
Thanks,
Andreas
[EMAIL PROTECTED] wrote:
Hi!
I'd just like t
).
Any hints are very welcome :-) I hope it is not one of the
"unsettled 2.6 kernel issues" cdrecord warns about :-/
Thanks and best regards,
Andreas
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://www.littletux.net
ICQ: 326674288System
---
K3b Versio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I suppose you are talking about bug #332781,
garbage characters in eterm on (amd)64 port.
Laurence,
I would like to help with this bug. I have created new
packages for libast and eterm, available at
http://littletux.homelinux.org/debian/pool/ma
5 matches
Mail list logo