From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Linker weirdness? (was: Assembler weirdness?)
Date: Sun, 18 May 2008 14:01:24 +1000 [thread overview]
Message-ID: <775b8d190805172101n114504cfm8221e5d73d0b642c@mail.gmail.com> (raw)
In-Reply-To: <DE9DB11C-C5B4-4647-A4B2-675C3D8D531C@mac.com>
please keep this off the list. you fixing something for a change.is as
interesting as my puppy shiiting outside.
good doggy,
brucee
On 5/18/08, Pietro Gagliardi <pietro10@mac.com> wrote:
> I fixed it by specifying in the mkfile to convert jamesmol.s to jmfixed.s or
> something.
>
> But now when I go to link I get these weird errors about undefined symbols
> in a function that they are not even related to.
>
> source: /n/sources/contrib/pietro/pgos.tar
> error list: /n/sources/contrib/pietro/pgos.err
>
> And yes, I plan to use the a.out(6). But now it just takes raw binary.
>
> On May 17, 2008, at 10:21 PM, Pietro Gagliardi wrote:
>
> > You mean ##? Okay, but since 8a doesn't have an option to issue the
> standard C preprocessor (cpp(1) - 8c has -p), I'll see what I can do.
> >
> > On May 17, 2008, at 9:44 PM, erik quanstrom wrote:
> >
> >
> > >
> > > > Hello. I'm trying to switch from GCC/NASM to the good old Plan 9 tools
> > > > to get a simple kernel I'm writing compiled and working with 9load
> > > > (which fortunately is Multiboot-compliant). But there is one file - an
> > > > 8a-ized hand-me-down interrupt service routine array - that is causing
> > > > problems. Running
> > > >
> > > > 8a /n/sources/contrib/pietro/jamesmol.s
> > > >
> > > > yields the errors in
> /n/sources/contrib/pietro/jamesmol.out. But if I
> > > > first preprocess with cpp(1), which produces
> /n/sources/contrib/pietro/
> > > > jamesmol.fixed, everything works fine with 8a. What's wrong?
> > > >
> > > > - Pietro
> > > >
> > > > PS - This is when I hate macros.
> > > >
> > >
> > > i believe 8c disapproves of string pasting.
> > >
> > > - erik
> > >
> > >
> > >
> >
> >
> >
>
>
>
next prev parent reply other threads:[~2008-05-18 4:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 1:38 [9fans] Assembler weirdness? Pietro Gagliardi
2008-05-18 1:44 ` erik quanstrom
2008-05-18 2:21 ` Pietro Gagliardi
2008-05-18 2:56 ` [9fans] Linker weirdness? (was: Assembler weirdness?) Pietro Gagliardi
2008-05-18 4:01 ` Bruce Ellis [this message]
2008-05-18 4:35 ` [9fans] Linker weirdness? Robert William Fuller
2008-05-18 4:45 ` Bruce Ellis
2008-05-18 12:02 ` [9fans] Linker weirdness? (was: Assembler weirdness?) erik quanstrom
2008-05-18 12:36 ` Pietro Gagliardi
2008-05-18 15:57 ` Richard Miller
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=775b8d190805172101n114504cfm8221e5d73d0b642c@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@9fans.net \
/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).