From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Chas Williams <chas@cmf.nrl.navy.mil>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: anyone build 2.3.42 for ppc?
Date: Sat, 05 Feb 2000 13:23:59 -0500 [thread overview]
Message-ID: <389C6ABF.1138CC1B@mandrakesoft.com> (raw)
In-Reply-To: 200002051456.JAA34961@borg.cmf.nrl.navy.mil
Chas Williams wrote:
>
> >In message <Pine.LNX.3.96.1000204232520.15802L-100000@mandrakesoft.mandrakesoft.com>,Jeff Garzik writes:
> >This patch is wrong. I fixed nvram to use initcalls.
> >If nvram doesn't load you have other problems.
>
> ok, i see the problem, with __initcall, which is missing in
> drivers/macintosh/nvram.c, so this patch is more correct, however it still
> doesnt work after making this change. i believe the reason is ld related,
> when vmlinux is linked, __initcall_nvram_init resides in macintosh.a along
> with another initcall function, __initcall_adb_init. after linking
> vmlinux only contains __initcall_adb_init:
Ah! The solution: follow the example in other makefiles, and create
'macintosh.o' not 'macintosh.a'. That is the only problem...
initcall gets removed during link if you use an 'ar' library. This is
why some of the core subsystems have been changed from 'ar' to 'ld
-r'... As this change stops the elimination of dead code, you must
ensure that no dead code exists by virtue of a bug-free Makefile and
Config.in system.
--
Jeff Garzik | See you at Linux Expo in Paris!
Building 1024 |
MandrakeSoft, Inc. |
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-05 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-04 22:04 anyone build 2.3.42 for ppc? Brad Parker
2000-02-04 22:18 ` Martin Costabel
2000-02-05 2:15 ` Chas Williams
2000-02-05 5:26 ` Jeff Garzik
2000-02-05 13:37 ` Chas Williams
2000-02-05 14:56 ` Chas Williams
2000-02-05 18:23 ` Jeff Garzik [this message]
2000-02-05 20:04 ` Chas Williams
2000-02-07 8:29 ` Brad Midgley
2000-02-07 9:28 ` Martin Costabel
2000-02-07 14:46 ` Dan Burcaw
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=389C6ABF.1138CC1B@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=chas@cmf.nrl.navy.mil \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).