From: Andrew B. <ad...@ii...> - 2009-08-10 11:29:15
|
On Fri, 2009-08-07 at 18:20 +0200, Heinz Wiesinger wrote: > On Monday 30 March 2009 23:01:29 Heinz Wiesinger wrote: > > On Monday 30 March 2009 22:53:56 you wrote: > > > On Mon, 2009-03-30 at 21:41 +0200, Heinz Wiesinger wrote: > > > > On Monday 30 March 2009 14:09:07 you wrote: > > > > > My Debian box has gcc-4.3 as the default gcc ccompiler, which is why > > > > > > > > you > > > > > > > > > get the warnings about no newline at the end of files. > > > > > > > > Well, I don't care about those really. If it would compile :/ > > > > > > Before I can make any fixes and say "It's fixed" I first need to be able > > > to recreate the error. And at the moment, even when using both gcc-4.2 > > > and 4.3 at my end, I'm unable to recreate the compile error. > > > > ok, that's fine. > > > > > > > Are you able to compile with 4.3 rather than 4.2? > > > > > > > > Nope. Slackware 12.2 comes with gcc-4.2.4. I could install another > > > > gcc, but that would not be considered clean and wouldn't help in > > > > providing a solution for other Slackware users. Suggesting a switch to > > > > another gcc is not considered a solution. > > > > I may be able to test against gcc-4.3 in Slackware's development > > > > version, but that is still far from a release. Apart from that I don't > > > > have such a system at the moment and it could take some time to set > > > > one up. > > > > > > OK, appreciate its an inconvenience, but I would like to at least know > > > whether this is contained to gcc-4.2 or whether it affects other users > > > as well. > > > > That's understandable. I will try to set a system up as soon as possible, > > which might be next weekend, but could also be later. > > I'll report my results here as soon as I have them. > > Wow, huge delay. Sorry about that :/ > I tested 1.10 and latest cvs on Slackware 13.0-rc2 (with gcc-4.3.3). 1.10 > still failed with one of the mentioned errors, but latest cvs compiled fine :) > > One small issue I found however is, that when using --libdir=/usr/lib64 > libpcsxcore gets installed in /usr/lib64 but the psemu plugins are installed > to /usr/lib/psemu (without the '64'). > > Again sorry for the huge delay. No probs - thanks so much for reporting that the CVS changes work! Can you raise a bug on the plugins not installing to lib64? Otherwise I'll forget ;) |