Xref: utzoo comp.sys.m68k:2040 comp.realtime:1059 comp.unix.questions:27517 Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!mit-eddie!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!src.honeywell.com!msi.umn.edu!cs.umn.edu!uc!uf!jeff From: jeff@uf.msc.umn.edu (Jeff Turner) Newsgroups: comp.sys.m68k,comp.realtime,comp.unix.questions Subject: Re: compiling 68000 code on a Sun 3 Message-ID: <3106@uc.msc.umn.edu> Date: 11 Dec 90 04:52:15 GMT References: <1990Dec7.145400.26717@funet.fi> Sender: news@uc.msc.umn.edu Reply-To: jeff@uf.UUCP (Jeff Turner) Organization: Minnesota Supercomputer Center, Minneapolis, MN Lines: 19 In article <1990Dec7.145400.26717@funet.fi> pl@news.funet.fi.tut.fi (Lehtinen Pertti) writes: > > Most problems you will get with loader, as it is not very easy > tell it to start addresses for code and data, we used simple catenation > with 'ld -N' and sun default address (0x2000) happens to be ok for us. The following LD command locates the code segment at address 0x10000 and places the data and BSS segments immediately after it. ld -T 10000 -d -e _start -o output.bin a.o b.o c.o ... The addition of a "-Tdata addr" would allow you to locate the data and BSS segments elsewhere (e.g. in RAM). -Jeff --- Jeff Turner Minnesota Supercomputer Center, Inc. (612) 626-0544 1200 Washington Avenue South jeff@msc.edu Minneapolis, Minnesota 55415