as68 error message

Anything QL Software or Programming Related.
Post Reply
swensont
Forum Moderator
Posts: 325
Joined: Tue Dec 06, 2011 3:30 am
Location: SF Bay Area
Contact:

as68 error message

Post by swensont »

As I'm converting all non-curses print calls to curses one, I've hit a snag on the program that I am porting.

Everything was compiling fine with Make. I found a few minor issues with main_c. I fixed the last error and now I get this message:

as68 main_s main_o
jas: (bytes not separately relocatable)

I can't find any documentation on as68, so I don't know what that means. I made no changes to the Makefile. The c compiler seems to like the code as it does not report any errors. I'm hoping someone has a clue what this message means.

Tim


swensont
Forum Moderator
Posts: 325
Joined: Tue Dec 06, 2011 3:30 am
Location: SF Bay Area
Contact:

Re: as68 error message

Post by swensont »

Looking at the as68 source code, there are a couple of ways to get this message:

if ( havebyte == 1 && rval != orval )

if ( rval != R_ABS && rval != R_FIRST )

if ( rval != R_ABS && rval != R_FIRST )

None of those look obvious as to what the problem is. Hopefully someone else has seen this and knows the solution.

Tim


User avatar
XorA
Site Admin
Posts: 1631
Joined: Thu Jun 02, 2011 11:31 am
Location: Shotts, North Lanarkshire, Scotland, UK

Re: as68 error message

Post by XorA »

Looks like it might be caused by access a word on odd byte boundary!


User avatar
ppe
Trump Card
Posts: 171
Joined: Tue Dec 14, 2010 10:48 am
Location: Espoo, Finland

Re: as68 error message

Post by ppe »

XorA wrote:Looks like it might be caused by access a word on odd byte boundary!
Unaligned struct member, perhaps?


User avatar
mk79
QL Wafer Drive
Posts: 1349
Joined: Sun Feb 02, 2014 10:54 am
Location: Esslingen/Germany
Contact:

Re: as68 error message

Post by mk79 »

Curious that it doesn't say a line number along with it. A few options, revert your changes in main_c and re-apply them, always checking when the error appears. Or have a look at main_s if something is fishy. I don't think its got anything to do with alignment. More some pointer usage problem (that the compiler accepts but is still wrong) or a weird name-clash.


Post Reply