From fnaumann@mail.cs.uni-magdeburg.de Mon Jul 12 12:36:29 2004 Subject: Re: [MiNT] Bug in FATFS Reply-To: gokmase@home.se From: "Joakim H=?ISO-8859-1?Q?=F6gberg"?= To: mint@fishpool.com Date: Mon, 12 Jul 2004 12:26:13 +0200 X-Mailer: NetMail ModWeb Module X-Sender: gokmase@home.se MIME-Version: 1.0 Message-ID: <1089627973.b4512400gokmase@home.se> Content-Type: text/plain; charset="ISO-8859-1" X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at fishpool.fi Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: gokmase@home.se Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by prinz.cs.uni-magdeburg.de id i6CAaCcA011283 Hi! >Actually this is a problem with the compiler. At >aleast here the editor >works ok but the compiler has always suffered from >this. Anyway, I Absolutely, the editor/interpreter has not had any problems with the double extension thingy at all here. It is the compiler for sure. >If you pass "test" it constructs "test.gfa", if you >pass "test.gfa" it >constructs "test.gfa.gfa". Not exactly a very good >way to handle this >but unfortunately this is how it was coded. It seems >to rely on the >original TOS file system to clip off the extra >extender at the first "." it Yeah, seems like it indeed. >Just setting the newfatfs OFF for the drive is enough >to make it work. >That I can verify, and I think also Gokmase will >agree. Yes :) >I did hack the binary in order to use the GFA >compiler on newfatfs. ;-) So, using a patched compiler would IMO clearly be the best solution. Or are there other apps coded with this peculiar behaviour? Regards, Joakim