vasm strange behaviour

Den · 07 December 2015, 20:19

Hello!

I've compiled latest versions of vasm and vlink on Windows 10 with MinGW and something strange happens

When I assemble any source with -Fhunkexe I get a file that is not an object module under 1.3 but works on 2.0.

When I assemble with -Fhunk and then link with -bamigahunk I get a file that can be run on both 1.3 and 2.0

I remember that I could get an 1.3 executable with a previous version of vasm with -Fhunkexe but I'm not sure if something has changed in hunk output module or if I've done something wrong when I compiled vasm...

I have zipped the source (not mine, a simple scrolling starfield), the executables and "my" vasmm68_mot if it's of any help: [removed since it wasn't needed]

Leffmann · 07 December 2015, 21:04

Specify -kick1hunks on the command line.

Den · 07 December 2015, 23:44

Thanks for the answer Leffman and for not telling me to RTFM

So, now vasm will output 2.04+ executables by default unless -kick1hunks is specified, and vlink will still produce 1.xx+ executables by default unless -Rshort is specified. Is that correct?

Thanks again.

phx · 12 December 2015, 15:24

Quote:

Originally Posted by Den

So, now vasm will output 2.04+ executables by default unless -kick1hunks is specified, and vlink will still produce 1.xx+ executables by default unless -Rshort is specified. Is that correct?

Indeed. Hm, I agree it looks a bit unfortunate.

07 December 2015, 20:19	#1
Den Registered User Join Date: Apr 2012 Location: Velaux / France Age: 56 Posts: 16	vasm strange behaviour Hello! I've compiled latest versions of vasm and vlink on Windows 10 with MinGW and something strange happens When I assemble any source with -Fhunkexe I get a file that is not an object module under 1.3 but works on 2.0. When I assemble with -Fhunk and then link with -bamigahunk I get a file that can be run on both 1.3 and 2.0 I remember that I could get an 1.3 executable with a previous version of vasm with -Fhunkexe but I'm not sure if something has changed in hunk output module or if I've done something wrong when I compiled vasm... I have zipped the source (not mine, a simple scrolling starfield), the executables and "my" vasmm68_mot if it's of any help: [removed since it wasn't needed] Last edited by Den; 07 December 2015 at 23:46. Reason: removed the unneeded linked archive

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Strange Prefs (non) behaviour.	khph_re	support.WinUAE	4	02 October 2010 14:34
Strange A600 behaviour	Gavilan	support.Hardware	9	08 July 2009 19:02
Strange guru behaviour!	deejaya	support.Other	11	31 January 2009 21:01
Strange behaviour in p. illusions	_ThEcRoW	support.Games	4	18 June 2007 18:17
strange sound behaviour in 0.8.27	Domenico	support.WinUAE	8	13 October 2006 11:24

07 December 2015, 21:04	#2
Leffmann Join Date: Jul 2008 Location: Sweden Posts: 2,269	Specify -kick1hunks on the command line.

07 December 2015, 23:44	#3
Den Registered User Join Date: Apr 2012 Location: Velaux / France Age: 56 Posts: 16	Thanks for the answer Leffman and for not telling me to RTFM So, now vasm will output 2.04+ executables by default unless -kick1hunks is specified, and vlink will still produce 1.xx+ executables by default unless -Rshort is specified. Is that correct? Thanks again.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)