From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Linker weirdness? (was: Assembler weirdness?)
Date: Sun, 18 May 2008 08:02:55 -0400 [thread overview]
Message-ID: <9b492a4ca1babd2743c6e3c8d03047ff@quanstro.net> (raw)
In-Reply-To: <DE9DB11C-C5B4-4647-A4B2-675C3D8D531C@mac.com>
> 8l -T0x100000 -o 8.out boot.8 cpuid.8 floppy.8 gdt.8 halt.8 harddisk.8 interrupt.8 jmtrue.8 keyboard.8 memory.8 multitask.8 onlyin.8 pci.8 syscall.8 time.8 timer.8 tone.8 video.8 x86.8 ../port/libpgosport.a
> initnonport: incompatible type signatures 4c81a129(gdt.8) and 97da8762(x86.8) for initgdt
> main: incompatible type signatures 4c81a129(timer.8) and 951b2e20(../port/libpgosport.a(main)) for inittimer
> simplelang: np: not defined
> simplelang: apm: not defined
> simplelang: gdt: not defined
apoligies in advance for addressing the actual question.
the default CFLAGS were changed recently on sources. the -T flag was added to the
defaults. this adds type signatures to .$O files. without -T type signatures are left
blank. the linker expects either all the signatures for a particular symbol to match
or to be blank.
incompatable signatures happen when the same external symbol is declared with
different types in different source files. the linker is picky. "uint" and "int" are not
compatable.
- erik
next prev parent reply other threads:[~2008-05-18 12:02 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
2008-05-18 4:35 ` [9fans] Linker weirdness? Robert William Fuller
2008-05-18 4:45 ` Bruce Ellis
2008-05-18 12:02 ` erik quanstrom [this message]
2008-05-18 12:36 ` [9fans] Linker weirdness? (was: Assembler weirdness?) 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=9b492a4ca1babd2743c6e3c8d03047ff@quanstro.net \
--to=quanstro@quanstro.net \
--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).