rlcarr@athena.mit.edu (Rich Carreiro) (02/15/89)
I asked this question about 10 days ago and got a number of
answers. Most blamed the problem on the 5.0 bugs. I have since
installed the 5.02 patch. I got the patches from the LBBS on 2/8/89.
My lc.lib has definitely been patched, and lcnb.lib is dated Jan 17, 1989.
Now for the problem:
I havve a program named gadget.c. It is John Draper's gadget tutorial program.
When I had 4.0x, I recompiled it with
lc -v -Lv gadget
It worked, but there were no gadget images (they weree pre-initialized and were
ending up in my fast RAM). I then compiled with
lc -v -abd -Lv gadget
THIS WORKED. IT SHOWED THE GADGETS PERFECTLY.
So along comes 5.0. I try
lc -v -abd -Lv gadget
and the linker dies with
Error 510: _IntuitionBase references unmerged ......
try -b0 option on LC.
etc, etc.
so I do
lc -v -b0 -abd -Lv gadget
and the same thing happens. I change -abd to -ad. Same error.
I change -ad to -abcd. Same error.
Someone, a Mark or Dan or Steve Riley sends me email saying that
I should do -ad, but in any case it will only work in 5.02.
I get 5.02 and apply all the patches. I compile the program with
lc -v -b0 -ad -Lv gadget
and the linker dies with the SAME error 510.
The only way I've been able to get the program to work is to use the CHIP
option to BLINK to force everything into chip RAM. I do not like
that solution. So, what am I doing wrong?
lc -v -abd -Lv gadget worked FINE with 4.0x
It (and any permuations of -a[bcd] and -b[0] will NOT work
with 5.0 or 5.02. I have the same setup now as with 4.0x.
Any explantions?
ARPA: rlcarr@athena.mit.edu
UUCP: {wherever}!mit-eddie!mit-athena!rlcarr
BITNET: rlcarr%athena.mit.edu@MITVMA.mit.edu
*******************************************************************************
* Rich Carreiro "Back off man, I'm a scientist." *
* rlcarr@athena.mit.edu - Dr. Peter Venkman *
*******************************************************************************tada@athena.mit.edu (Michael Zehr) (02/15/89)
In article <9254@bloom-beacon.MIT.EDU> rlcarr@athena.mit.edu (Rich Carreiro) writes: >I asked this question about 10 days ago and got a number of >answers. Most blamed the problem on the 5.0 bugs. I have since >installed the 5.02 patch. I got the patches from the LBBS on 2/8/89. > [...] >The only way I've been able to get the program to work is to use the CHIP >option to BLINK to force everything into chip RAM. I do not like >that solution. So, what am I doing wrong? I had similar problems, both with 5.0 and 5.02. When I called the Lattice technical support people, they offered the following fix: put all your 'chip' declarations in one module, with no non-chip declarations. from your other modules, declare the references as 'extern chip ...' then link everything normally. i'm not sure it will fix your problems, but it fixed mine. (i was getting "not an object module" errors when trying to run things...) hope this helps... -michael j zehr
mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) (02/16/89)
In article <9256@bloom-beacon.MIT.EDU> tada@athena.mit.edu (Michael Zehr) writes: <In article <9254@bloom-beacon.MIT.EDU> rlcarr@athena.mit.edu (Rich Carreiro) writes: <>I asked this question about 10 days ago and got a number of <>answers. Most blamed the problem on the 5.0 bugs. I have since <>installed the 5.02 patch. I got the patches from the LBBS on 2/8/89. <> [...] <>The only way I've been able to get the program to work is to use the CHIP <>option to BLINK to force everything into chip RAM. I do not like <>that solution. So, what am I doing wrong? < <I had similar problems, both with 5.0 and 5.02. When I called the <Lattice technical support people, they offered the following fix: < <put all your 'chip' declarations in one module, with no non-chip <declarations. < <from your other modules, declare the references as 'extern chip ...' I'm not sure the 'chip' is needed. I know it isn't if you use -b0. As an alternative, you ought to be able to inlclude the 'chip' structures in with other source, declare them as 'chip' with the appropriate keyword, and then compile normally. This will _not_ work with 5.0; you have to have 5.02. <mike -- And then up spoke his own dear wife, Mike Meyer Never heard to speak so free. mwm@berkeley.edu "I'd rather a kiss from dead Matty's lips, ucbvax!mwm Than you or your finery." mwm@ucbjade.BITNET
scott@applix.UUCP (Scott Evernden) (02/19/89)
In article <9254@bloom-beacon.MIT.EDU> rlcarr@athena.mit.edu (Rich Carreiro) writes: >Error 510: _IntuitionBase references unmerged ...... try declaring IntuitionBase as an extern: extern IntuitionBase *IntuitionBase; Both this and GfxBase are now declared in the libs in V5- just to make things difficult. -scott