From: rob@atvetsystems.com (Robert Tillyard)
Subject: [Unix-jun72] Readme written: needs checking
Date: Wed, 7 May 2008 15:11:42 +0100 [thread overview]
Message-ID: <E153B7D2-A409-403C-8029-A5AF31C08F1A@atvetsystems.com> (raw)
In-Reply-To: <20080507101930.GT2793@myrtle.kent.ac.uk>
On 7 May 2008, at 11:19, P.A.Osborne wrote:
> On Wed, May 07, 2008 at 07:28:42PM +1000, Warren Toomey wrote:
>> Is there __OSX__ or similar? If there is, simply add
>>
>> && !defined(__OSX__)
>>
>> to that second line, which is around line 71 in tools/apout/
>> defines.h.
>
> Warren,
>
> __APPLE__ does part of the trick, then we get:
>
> cc -static -g aout.o branch.o bsd_ioctl.o bsd_signal.o bsdtrap.o cpu.o
> debug.o double.o ea.o fp.o itab.o ke11a.o magic.o main.o single.o
> v1trap.o v7trap.o -o apout -lm
> ld_classic: can't locate file for: -lcrt0.o
> collect2: ld returned 1 exit status
> make[1]: *** [apout] Error 1
>
>
> At this point I am in the midst of Apple butchering tools to produce
> universal binaries (powerpc and x64), will continue to swear at this
> (or just give in and install FreeBSD under VMWare :-) ).
>
> Paul
Remove the -static
Regards, Rob.
next prev parent reply other threads:[~2008-05-07 14:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 1:33 Warren Toomey
2008-05-07 2:35 ` John Cowan
2008-05-07 3:05 ` Tim Newsham
2008-05-07 3:19 ` Warren Toomey
2008-05-07 5:11 ` John Cowan
2008-05-07 6:18 ` Warren Toomey
2008-05-07 3:29 ` [Unix-jun72] simh patch fails Warren Toomey
2008-05-07 2:44 ` [Unix-jun72] Readme written: needs checking Jim Capp
2008-05-07 3:36 ` Jim Capp
2008-05-07 3:43 ` Warren Toomey
2008-05-07 3:59 ` Jim Capp
2008-05-07 4:01 ` Jim Capp
2008-05-07 5:22 ` Johan Beisser
2008-05-07 8:40 ` P.A.Osborne
2008-05-07 9:28 ` Warren Toomey
2008-05-07 10:19 ` P.A.Osborne
2008-05-07 14:11 ` Robert Tillyard [this message]
2008-05-07 14:29 ` P.A.Osborne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E153B7D2-A409-403C-8029-A5AF31C08F1A@atvetsystems.com \
--to=rob@atvetsystems.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).