[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-12-23 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 User sparcmoz changed the following: What|Old value |New value

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-12-18 Thread rene
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 User rene changed the following: What|Old value |New value

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-12-10 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 --- Additional comments from [EMAIL PROTECTED] Sat Dec 10 14:24:24 -0800 2005 --- verified in cws_src680_unxlngs04

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-11-16 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 --- Additional comments from [EMAIL PROTECTED] Wed Nov 16 02:25:32 -0800 2005 --- I have checked this builds OK with g++-3.4 (debian/unstable) as well as version

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-09-23 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 User sparcmoz changed the following: What|Old value |New value

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-07-26 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 User sparcmoz changed the following: What|Old value |New value

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-07-25 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 --- Additional comments from [EMAIL PROTECTED] Mon Jul 25 04:00:49 -0700 2005 --- This builds: case typelib_TypeClass_HYPER: case typelib_TypeClass_UNSIGNED_HYPER:

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-07-25 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 --- Additional comments from [EMAIL PROTECTED] Mon Jul 25 04:11:23 -0700 2005 --- testtools builds OK using gcc-3.3 with j2sdk1.4.1 although bridges has been

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-07-25 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 User sparcmoz changed the following: What|Old value |New value

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-07-25 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 --- Additional comments from [EMAIL PROTECTED] Mon Jul 25 05:43:11 -0700 2005 --- some success with this: case typelib_TypeClass_HYPER: case

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-07-23 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 User sparcmoz changed the following: What|Old value |New value

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-07-04 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 --- Additional comments from [EMAIL PROTECTED] Mon Jul 4 06:55:02 -0700 2005 --- I had a guess based on sparc cc50 but not quite right... [EMAIL

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-07-04 Thread sparcmoz
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 User sparcmoz changed the following: What|Old value |New value

[porting-issues] [Issue 51545] error: memory input 0 is not directly addressable on linux sparc gcc-4. 0

2005-07-04 Thread sb
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51545 --- Additional comments from [EMAIL PROTECTED] Mon Jul 4 07:49:46 -0700 2005 --- What *might* help is to replace __asm__(... m(nRegReturn) ); with void *