M68k assembler under cygwin
William A. Gatliff
bgat@billgatliff.com
Wed Dec 18 08:10:00 GMT 2002
Bruce:
Use .equ SYMBOL, EXPRESSION instead of your construct, perhaps? From
the as info pages:
File: as.info, Node: Equ, Next: Equiv, Prev: Endif, Up: Pseudo Ops
`.equ SYMBOL, EXPRESSION'
=========================
This directive sets the value of SYMBOL to EXPRESSION. It is
synonymous with `.set'; *note `.set': Set..
HTH,
b.g.
On Wed, Dec 18, 2002 at 10:42:54AM -0000, Bruce Adams wrote:
>
>
> Hi,
> I am trying to assemble some existing m68k assembler code under gcc. I
> have for the time being suspended my attempts to build a cross that works
> from cygwin and opted to use the prebuilt rtems compiler until I can get
> our existing codebase and especially the assembly to build & link. (No
> point
> trying to use gcc 3.2 and the STL if I can't do that).
> Ideally I want a cygwin to m68k-elf or m68k-nucleus if such a thing exists.
> Anyway the assembly code itself is basically sound. It can be made to
> work with Crosscode ASM68000, Green Hills & Metrowerks Code Warrior, though
> I have had issues trying to get it working with the stricter Microtec
> compiler.
> I have several problems with gcc. Firstly it reports errors relative
> to positions in a temporary file rather than the original file.
> Worse it does not seem to recognise much of the assembler I feel it should.
> For example EQU directives like:
>
> sf_BOOTROM_COMPATIBILTY equ 2
>
> Example output follows:
>
> C:\BruceA\builds\compiler\mak>create /cg wrench
> WRENCH Component (Firmware)....
> ..\src\bhdrdata.s (m68k-rtems-gcc.exe -xassembler -c -save-temps -v) ->
> ..\gtaro
> bj\wrench\bhdrdata.obj
> m68k-rtems-gcc -v -x assembler-with-cpp -mri -Wp,-P -DctD_NUCLEUS -I..\src
> ..\sr
> c\bhdrdata.s -o ..\gtarobj\wrench\bhdrdata.obj
> Reading specs from /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.3/specs
> gcc version 2.95.3 20010315 (release)
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.3/cpp0.exe -lang-asm -v -I..\src -$
> -Dmc
> 68000 -Drtems -D__rtems__ -D__ELF__ -D__mc68000__ -D__rtems__ -D__rtems__
> -D__EL
> F__ -D__mc68000 -D__rtems -Asystem(rtems) -Acpu(mc68000) -Acpu(m68k)
> -Amachine(m
> 68k) -D__ASSEMBLER__ -D__HAVE_68881__ -Dmc68020 -D__mc68020 -D__mc68020__
> -DctD_
> NUCLEUS -P ..\src\bhdrdata.s
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccO
> gBeUU.s
> GNU CPP version 2.95.3 20010315 (release) (68k, Motorola syntax)
> #include "..." search starts here:
> #include <...> search starts here:
> ../src
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.3/include
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.3/../../../../m68k-rtems/include
> End of search list.
> The following default directories have been omitted from the search path:
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.3/../../../../include/g++-3
> /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.3/../../../../m68k-rtems/sys-include
> End of omitted list.
> /opt/rtems/m68k-rtems/bin/as.exe -mc68020 -o
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/
> LOCALS~1/Temp/ccCsSTxJ.o
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeU
> U.s
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeUU.s: Assembler
> messages:
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeUU.s:194: Error:
> Unknown o
> perator -- statement `sf_bootrom_compatibilty equ 2' ignored
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeUU.s:195: Error:
> Unknown o
> perator -- statement `checked by bootstrap for compatiblity' ignored
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeUU.s:196: Error:
> Unknown o
> perator -- statement `with MINERVA firmware.' ignored
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeUU.s:200: Error:
> Unknown o
> perator -- statement `section boot_header' ignored
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeUU.s:206: Error:
> Unknown o
> perator -- statement `start of Bootstrap header block' ignored
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeUU.s:211: Error:
> Unknown o
> perator -- statement `section panel_header' ignored
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeUU.s:213: Error:
> Unknown o
> perator -- statement `start of MINERVA header block' ignored
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeUU.s:216: Error:
> Unknown o
> perator -- statement `xref _MINERVA_START' ignored
> /cygdrive/c/DOCUME~1/BADAMS~1.TEP/LOCALS~1/Temp/ccOgBeUU.s:216: Error:
> Unknown o
> perator -- statement `entry point to start up the MINERVA' ignored
>
> OPUS MAKE: Shell line exit status 1. Stop.
>
> OPUS MAKE: Shell line exit status 3. Stop.
>
> Any idea what could be going wrong?
> Regards,
> Bruce A.
>
>
> ============================================================================
> Any opinions expressed in this e-mail are those of the individual and not
> necessarily those of Tyco Electronic Product Group.
>
> Any prices for the supply of goods or services are only valid if supported
> by a formal written quotation.
>
> This e-mail and any files transmitted with it, including replies and
> forwarded copies (which may contain alterations) subsequently transmitted
> from Tyco Electronic Product Group are confidential and solely for the use
> of the intended recipient.
>
> If you are not the intended recipient or the person responsible for
> delivery to the intended recipient, be advised that you have received this
> e-mail in error and that any use is strictly prohibited. In this event,
> please notify us via e-mail at 'helpdesk.tepg@tycoint.com' or telephone on
> 0121 255 6499 and then delete the e-mail and any copies of it.
> ============================================================================
>
>
>
>
>
>
> ------
> Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
>
--
Bill Gatliff
Embedded systems and Free Software. Yea, it *is* all that!
http://billgatliff.com
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
More information about the crossgcc
mailing list