| To: | oe.hansen@xxxxxxxxxxxxxxxxxxx, Jarkko Santala <jake@xxxxxxx> |
|---|---|
| Subject: | Re: Another case of "getfh failed: Operation not permitted" |
| From: | Seth Mos <knuffie@xxxxxxxxx> |
| Date: | Thu, 12 Jul 2001 22:33:17 +0200 |
| Cc: | "linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <01071222192900.01654@citadel.oehansen.pp.se> |
| References: | <Pine.OSF.4.33.0107122242050.32548-100000@torni.hel.fi.ssh.com> <Pine.OSF.4.33.0107122242050.32548-100000@torni.hel.fi.ssh.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
At 22:19 12-7-2001 +0200, Orn E. Hansen wrote:
fimmtudagur 12. júlí 2001 21:43, Jarkko Santala skrifaði: > > Yep, I read it and that's why I tried it. ;) The linux/Makefile did claim > the standard RedHat 7.1 gcc to be usable though... > It's machine dependent. There are people using this combination that exhibit problems. I even do, I don't use it because it tends to cause vague problems for which I don't have time to debug them. I have removed gcc from my test systems so I don't accidentally do. I was fighting weird problems to day with a utility that loads the firmware in Eicon Diva Server cards. It was givinginvalid argument messages untill I replaced the compiler with kgcc. I also have a number of userspace utility's that don't compile with gcc. Note that this is with gcc-2.96-85 So updated or not, it still sucks in my not so humble opinion. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | slackware 8.0, daedalus |
|---|---|
| Next by Date: | Re: Another case of "getfh failed: Operation not permitted", Juha Saarinen |
| Previous by Thread: | Re: Another case of "getfh failed: Operation not permitted", Orn E. Hansen |
| Next by Thread: | slackware 8.0, daedalus |
| Indexes: | [Date] [Thread] [Top] [All Lists] |