[comp.sys.amiga.tech] BLINK

wakres01@pa.usl.edu (1712 Stelly John B) (06/02/90)

Help  !!
Blink from Lattice (5.04) is giving me the following error:
UNKNOWN Symbol:DIstance for DataReloc16> 32768

My code compiles fine, but can't be linked !!!
I think I need to use a different c.lib or something like that, if so which ?


John B Stelly III
wakres01@pa.usl.edu

jmeissen@oregon.oacis.org (John Meissen) (06/02/90)

In article <9334@rouge.usl.edu> wakres01@pa.usl.edu (1712 Stelly John B) writes:
>
>Help  !!
>Blink from Lattice (5.04) is giving me the following error:
>UNKNOWN Symbol:DIstance for DataReloc16> 32768

This is a fairly common and simple one. In the default addressing mode
data must fall within a 64K block. The offset field has a range of +/-32K.
In this case the linker has come across a reference to a data item in
the data section that is outside the 64K range.
More than likely, your data space has gotten too big. A poor solution
is to compile with -b0. A better solution is to use AllocMem to allocate
large data items.
-- 
John Meissen .............................. Oregon Advanced Computing Institute
jmeissen@oacis.org        (Internet) | "That's the remarkable thing about life;
..!sequent!oacis!jmeissen (UUCP)     |  things are never so bad that they can't
jmeissen                  (BIX)      |  get worse." - Calvin & Hobbes

rick@tmiuv0.uucp (06/04/90)

In article <9334@rouge.usl.edu>, wakres01@pa.usl.edu (1712 Stelly John B) writes:
> Help  !!
> Blink from Lattice (5.04) is giving me the following error:
> UNKNOWN Symbol:DIstance for DataReloc16> 32768
> 

Just looking at that error message, it appears that you're using a 16-bit
pointer rather than a long (32-bit) pointer.

> My code compiles fine, but can't be linked !!!
> I think I need to use a different c.lib or something like that, if so which ?
> 
> 
> John B Stelly III
> wakres01@pa.usl.edu
-- 
  .-------------------------------------------------------------------------.
 / [- O] Rick Stevens (All opinions are mine. Everyone ignores them anyway.) \
|    ?   +--------------------------------------------------------------------|
|    V   | uunet!zardoz!tmiuv0!rick             (<-- Work (ugh!))             |
|--------+ uunet!zardoz!xyclone!sysop           (<-- Home Unix (better!))     |
|  uunet!perigrine!ccicpg!conexch!amoeba2!rps2  (<-- Home Amiga (Best!!)      |
 \ 75006.1355@compuserve.com (CIS: 75006,1355)  (<-- CI$)                    /
  `-------------------------------------------------------------------------'
"I was Caesarean born.  When I leave the house, I use the window."
                                         - Steven Wright

S.J.Raybould@fulcrum.bt.co.uk (Simon Raybould) (06/06/90)

In article <9334@rouge.usl.edu> wakres01@pa.usl.edu (1712 Stelly John B) writes:
>
>Help  !!
>Blink from Lattice (5.04) is giving me the following error:
>UNKNOWN Symbol:DIstance for DataReloc16> 32768

Compile with the -b0 option with lc


Cheers,

	Sie.

+-=-=-=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
|   British Telecom Fulcrum  | name : Simon John Raybould   {^.^}   |
|   Fordrough Lane           | path : sie@fulcrum.bt.co.uk   \~/    |
|   Birmingham               +-----------+--------------------------|
|   B9 5LD                   |   //      | AMIGA B2000HD 3MB 8088BB |
|   ENGLAND                  | \X/AMIGA  | Lattice C V5.05          |
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-=-+

jmeissen@oregon.oacis.org (John Meissen) (06/06/90)

In article <9334@rouge.usl.edu>, wakres01@pa.usl.edu (1712 Stelly John B) writes:
> Help  !!
> Blink from Lattice (5.04) is giving me the following error:
> UNKNOWN Symbol:DIstance for DataReloc16> 32768

I responded to this earlier, but I think it went out e-mail instead of on the
net and bounced back. The problem is that the data section has grown to larger
than 64K. If it was a reference to an external it would have a symbol name. The
fact that it is "UNKNOWN" means that it is a reference to the module's own
data section, and the fixup offset after merging exceeds 32768.

Probably has some large arrays declared somewhere. The solution is to use
AllocMem to allocate the large data structures.

-- 
John Meissen .............................. Oregon Advanced Computing Institute
jmeissen@oacis.org        (Internet) | "That's the remarkable thing about life;
..!sequent!oacis!jmeissen (UUCP)     |  things are never so bad that they can't
jmeissen                  (BIX)      |  get worse." - Calvin & Hobbes