Post, Mark K wrote: > Here's the first of the three patches I promised. I'm having definite > problems with the remaining two. This is essentially Wolfgang's patch > updated to match the 7.4 version of the affected modules.
OK, so we work around what appears to be a gcc namespace problem by renaming those printf function to xprintf ? works for me, although I don't really like it. The code example I sent out yesterday seemed to indicate pretty clearly that it is a gcc problem - ie. turning optimization off avoids the problem. My suggestion is - - let's work with Mark patches in order to get as far as we can, but I don't think this is the way to fix the problem. - identify whether we have a real gcc problem here or just lack of c++ skills :-) What do the SAP guys say about these apparent gcc problems ? gcc 3.2 is a public release, although it is undoubtedly also "bleeding edge". /per -- regards, Per Jessen, Zurich http://www.enidan.com - home of the J1 serial console. Windows 2001: "I'm sorry Dave ... I'm afraid I can't do that." _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
