9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Chris McGee <sirnewton_01@yahoo.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Linker and duplicate symbols
Date: Thu,  8 Sep 2016 20:48:21 -0400	[thread overview]
Message-ID: <63814C1E-B962-4221-B9E6-2B1BBDBB55F7@yahoo.ca> (raw)
In-Reply-To: <91091b7db7ee00347dfc22bd3d9ab312@hamnavoe.com>

Thanks Richard,

I traced it down to a symbol being brought in from libc that brought in other symbols that collided with ones on the kernel.

Btw, with your latest changes I have merged them in with the latest 9front and its running on my Pi 1 and Pi 2.

Only weird problem is when I do fshalt -r. My pi2 goes unstable with panics on reboot. Cold reset brings it back to normal.

Does your latest code work on Pi zero? I don't yet have one to test it.

Chris

On Sep 2, 2016, at 12:11 PM, Richard Miller <9fans@hamnavoe.com> wrote:

>> Is it that the linker prefers a symbol from a .5 file over the .a file?
> 
> I believe it's supposed to pick the first one it finds.  Object files and
> libraries are processed in the order in which they appear on the command line.
> On my system proc.5 appears before libc.a in the ld command, and libc.a(sleep.5)
> doesn't contain any symbols other than sleep, so there should be no reason
> for ld to pull it in from the library.
> 
> 




  reply	other threads:[~2016-09-09  0:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02  2:34 Chris McGee
2016-09-02 10:20 ` Richard Miller
2016-09-02 15:56   ` Chris McGee
2016-09-02 16:11     ` Richard Miller
2016-09-09  0:48       ` Chris McGee [this message]
2016-09-09  8:31         ` Richard Miller
2016-09-09 14:55           ` Chris McGee
2016-09-09 16:37             ` Richard Miller
2016-09-02 16:12     ` cinap_lenrek
2016-09-02 20:00       ` Chris McGee
2016-09-02 22:34         ` Steve Simon
2016-09-03 16:58           ` Chris McGee

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=63814C1E-B962-4221-B9E6-2B1BBDBB55F7@yahoo.ca \
    --to=sirnewton_01@yahoo.ca \
    --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).