OK, I think I spotted the problem. In sdld.c/sdld_init(), a target autodetection is performed, relying on argv[0] (passed from the caller, main()). Internet said, that COMMAND.COM mangles argv[0] - I don't know the exact details but I'd say it encloses it into double-quotes) (this might be also the case in WXP using COMMAND.COM - somebody can check this, and if true, this can be used during debugging).
I would recommend some diagnostic output in case the autodetection fails, and/or an output of the detected "values" of *target* and *sdld* variables upon some command-line switch. A workaround "target force" through some command-line option (which could be passed from sdcc through -Wl,xxx) would be welcome. JW ----- Original Message --------------- >So, is this (the unexpected warnings) a Win98-specific problem? >Are there any substantial system calls involved in deciphering the >capabilities of the linker (which would lead to rejection of them)? That >sounds strange. > ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
