Issue 24980 - cannot build toolkit without -fpermissive
Summary: cannot build toolkit without -fpermissive
Status: CLOSED FIXED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: 680
Hardware: Sun Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: Frank Schönheit
QA Contact: issues@porting
URL:
Keywords:
: 25152 25787 26172 (view as issue list)
Depends on:
Blocks:
 
Reported: 2004-02-01 20:59 UTC by sparcmoz
Modified: 2004-03-14 18:37 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
cd toolkt; patch -p0 < toolkit.diff (3.43 KB, patch)
2004-02-03 08:33 UTC, sparcmoz
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description sparcmoz 2004-02-01 20:59:04 UTC
fresh update from cws_src680_ooo20031216

these errors become warnings with -fpermissive

jim@sun:~/680/o2_src/toolkit$ uname -a
Linux sun 2.4.18 #1 SMP Mon Jan 27 14:07:39 EST 2003 sparc64 GNU/Linux

jim@sun:~/680/o2_src/toolkit$ g++ --version
g++ (GCC) 3.3.3 20040110 (prerelease) (Debian)


/home/jim/680/o2_src/toolkit/source/awt/vclxspinbutton.cxx: In member function
`virtual void toolkit::VCLXSpinButton::setValue(long int)':

/home/jim/680/o2_src/toolkit/source/awt/vclxspinbutton.cxx:193: error: assuming
pointer to member `void SpinButton::SetValue(long int)'

/home/jim/680/o2_src/toolkit/source/awt/vclxspinbutton.cxx:193: error: (a
pointer to member can only be formed with `&SpinButton::SetValue')

and 209, 215, 221, 227, 233, 239, 245

dmake:  Error code 1, while making '../../unxlngs.pro/slo/vclxspinbutton.obj'
---* TG_SLO.MK *---
Comment 1 Martin Hollmichel 2004-02-02 10:26:18 UTC
mh->mt: please have a look.
Comment 2 malte_timmermann 2004-02-02 10:33:42 UTC
MT->FS: Seems to be yours...
Comment 3 Frank Schönheit 2004-02-02 12:54:15 UTC
replacing "SpinButton::SetValue" with "&SpinButton::SetValue" should do here,
IIRC (had some similar problem in another file). Same in lines 209, 215, 221,
227, 233, 239, 245.

sparcmoz, do you mind trying this?
Comment 4 sparcmoz 2004-02-02 20:07:33 UTC
yes, it will build OK without -fpermissive after replacing those
"SpinButton::SetValue" with "&SpinButton::SetValue". I also rebuilt the whole
toolkit module without -fpermissive and no other errors were found.

Comment 5 Frank Schönheit 2004-02-03 08:11:46 UTC
great - should I check it in, or could you (who you're already working on this
branch) do this?
Comment 6 sparcmoz 2004-02-03 08:31:09 UTC
I will attach the patch file now. Please you commit this since I do not like to
make a change that affects all platforms, especially as I have never committed
anything yet ;)

Anyway I do not know what branch I am "working on" since i am updating from
cws_src680_ooo20031216 which is "closed".
Comment 7 sparcmoz 2004-02-03 08:33:09 UTC
Created attachment 12852 [details]
cd toolkt; patch -p0 < toolkit.diff
Comment 8 Frank Schönheit 2004-02-03 08:47:38 UTC
ehm, well, with branch I meant cws_src680_ooo20031216 ...
Thanks for the patch file - I am going to check into which processes I can embed
the checkin ...

fs->mh: Since we're not building without -fpermissive, I do not see any sense in
putting this issue into a CWS - it cannot be verified there. What's the process
for getting such changes in the tree?
Comment 9 sparcmoz 2004-02-03 09:09:11 UTC
Re: "Since we're not building without -fpermissive,"

I think waratah made all the changes to remove -fpermissive from 680, and this
is in all(?) the solenv/inc/platform.mk files --> "# -fpermissive should be
removed as soon as possible"

i did already build all cws_src680_ooo20031216 without -fpermissive only until
after it closed :( But maybe this time it is because I have gone to gcc 3.3.3?

anyway I do not mean to cause any problems here, maybe it is invalid now, but i
suppose it is best to fix as it will become a problem eventually?

Maybe let it wait until a new branch is provide for porting, no-one else seems
to be building this just now?

 
Comment 10 Frank Schönheit 2004-02-03 13:18:03 UTC
I wouldn't close this one as invalid, it's certainly worth fixing. However, I am
just wondering where to check in the fix, and I hope Martin can enlighten me here :)
Comment 11 Frank Schönheit 2004-02-05 07:53:58 UTC
accepting
Comment 12 pavel 2004-02-07 09:42:09 UTC
JFYI: it seems to be also on SRC680_m24 as of today.
Comment 13 Frank Schönheit 2004-02-09 08:33:30 UTC
*** Issue 25152 has been marked as a duplicate of this issue. ***
Comment 14 pavel 2004-02-12 16:57:25 UTC
I fixed this issue on just opened cws_src680_ooo20040225.
Comment 15 Frank Schönheit 2004-02-16 09:02:13 UTC
thanks!
Comment 16 pavel 2004-02-25 17:02:33 UTC
*** Issue 25787 has been marked as a duplicate of this issue. ***
Comment 17 jens-heiner.rechtien 2004-03-02 16:52:42 UTC
Verified.
Comment 18 pavel 2004-03-05 18:21:47 UTC
*** Issue 26172 has been marked as a duplicate of this issue. ***
Comment 19 pavel 2004-03-14 18:37:07 UTC
Fixed in cws_src680_ooo20040329.

Closing.