![]() |
![]() |
#1 |
This cat is no more
![]() Join Date: Dec 2004
Location: FRANCE
Age: 51
Posts: 7,118
|
vasm "undefined symbol" is driving me nuts
Is there an option in vasm to stop on error when symbol isn't found instead of declaring it as external?
I get a lot of unresolved symbols when linking, just because some symbols aren't defined and that's VERY annoying since I have to search in the asm source for the symbol instead of getting the line of the error directly |
![]() |
![]() |
#2 |
Registered User
![]() Join Date: Jul 2015
Location: The Netherlands
Posts: 3,299
|
Hmm, I don't think you generally can.
You can kind of do something similar as long as you only have one .asm file, by using -Fbin. That'll give errors during assembly for any symbol not defined in the .asm file being assembled. However, the -Fbin format can't resolve external dependencies so it's probably not going to fix the problem. |
![]() |
![]() |
#3 |
Natteravn
![]() Join Date: Nov 2009
Location: Herford / Germany
Posts: 2,318
|
Of course you can: -x
|
![]() |
![]() |
#4 |
Registered User
Join Date: Feb 2012
Location: #DrainTheSwamp
Posts: 4,545
|
this is somehow related, since I got that error message too.
I try to build an object file from the code below and I only get an outputfile, which looks like a debug file: Code:
* * SAS server startup module * Copyright 1995 NewTek, Inc. * machine generated -- do not edit * xdef __XCEXIT xref __Startup xref __Shutdown xref _ServerDesc section text,code moveq #0,d0 rts dc.l $04121994 dc.l $2 dc.l $100 dc.l __Startup dc.l __Shutdown dc.l _ServerDesc __XCEXIT: dc.l $0 dc.l $0 dc.l $0 end with vasm -m68020 -Fbin serv_s.a I get the undefined symbol message. I need a gcc compatible object file. |
![]() |
![]() |
#5 |
Natteravn
![]() Join Date: Nov 2009
Location: Herford / Germany
Posts: 2,318
|
This is a perfectly valid source. Three undefined symbols: __Startup, __Shutdown and _ServerDesc. All three are even declared by XREF. Having -x or not is irrelevant here.
You get "undefined symbol" with -Fbin, because -Fbin generates a raw binary output file. It cannot do that with unresolved symbol references. You rather want to generate an object file, where such symbol references are allowed and resolved by a linker. Use -Fhunk for AmigaOS hunk-format object files, or -Faout for Unix a.out format, supported by gcc. |
![]() |
![]() |
#6 |
This cat is no more
![]() Join Date: Dec 2004
Location: FRANCE
Age: 51
Posts: 7,118
|
-x is what I was looking for, thanks!
|
![]() |
![]() |
#7 |
Registered User
Join Date: Feb 2012
Location: #DrainTheSwamp
Posts: 4,545
|
|
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
"Voices8" 8 Channel Soundtracker "DemoSongI" song - "This is the Amiga with 8 Voices" | DemosongIHunter | request.Music | 45 | 23 May 2022 20:07 |
PFS3AIO is driving me nuts - help :( | Nostromo | support.Apps | 4 | 07 September 2017 16:14 |
Reference to undefined symbol __ldivu / __lmodu | iliak | Coders. C/C++ | 8 | 25 July 2016 00:01 |
AsmOne: Undefined symbol | copse | Coders. Asm / Hardware | 2 | 02 April 2012 01:41 |
Undefined symbol bsr.b init_bitmaps | VoltureX | Coders. General | 12 | 13 November 2011 16:11 |
|
|