From: Lou Langholtz <ldl@chpc.utah.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: problem building 2.3.47: no macintosh.a file
Date: Mon, 28 Feb 2000 19:03:09 -0700 [thread overview]
Message-ID: <38BB28DD.BE1E320E@chpc.utah.edu> (raw)
In-Reply-To: 38BB1E89.35A75737@chpc.utah.edu
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
Lou Langholtz wrote:
> When trying to compile the 2.3.47 linux distribution from a kernel.org
> mirror, I don't get a macintosh.a file built in my drivers/macintosh/
> directory. As a matter of fact, I don't seem to get any macintosh
> drivers built in that directory as there's no .o files at all. Anyone
> else experience this? I've tried poking around to discover where the
> error could be but so far I'm clueless about this. Am I doing something
> wrong with my .config configuration info? I've attached my .config file
> in case this could be it and someone could check it. Any other
> possibilities?
Aha! I found I needed to change (fix?) drivers/Makefile to essentially add in
the macintosh subdirectory like for CONFIG_MAC but for CONFIG_PPC. I've
attached this context diff.
> BTW: I did have to make some minor changes to get even so far as to try
> linking it all together. I've attached the context diff of my mem.c file
> which I had to change to get it to compile. Could my simple change be
> the right thing to have done for the mem.c file???
Now the linker gets the macintosh.a stuff but spews out about some undefined
references and fails. I suspect I may be able to fix this by changing my
configuration. If anybody knows better, please let me know too. The actual
undefined references are to: find_via_pmu, pmu_poll, backlight_level,
pmu_set_brightness, and vgacon_remap_base.
Advanced thanks ;-)
[-- Attachment #2: cdiff --]
[-- Type: text/plain, Size: 328 bytes --]
*** drivers/Makefile.orig Thu Feb 17 10:57:13 2000
--- drivers/Makefile Mon Feb 28 18:45:54 2000
***************
*** 52,57 ****
--- 52,62 ----
MOD_SUB_DIRS += video
endif
+ ifdef CONFIG_PPC
+ SUB_DIRS += macintosh
+ MOD_SUB_DIRS += macintosh
+ endif
+
ifdef CONFIG_MAC
SUB_DIRS += macintosh
MOD_SUB_DIRS += macintosh
next prev parent reply other threads:[~2000-02-29 2:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-29 1:19 problem building 2.3.47: no macintosh.a file Lou Langholtz
2000-02-29 2:03 ` Lou Langholtz [this message]
2000-02-29 2:58 ` Powerbook code in 2.3.x [was Re: problem building 2.3.47: no macintosh.a file] phandel
2000-02-29 5:31 ` Powerbook code in 2.3.x [was Re: problem building 2.3.47: nomacintosh.a file] Lou Langholtz
[not found] <Pine.LNX.3.96L.1000228205949.7447A-100000@unix48.andrew.cmu.edu>
2000-02-29 2:39 ` problem building 2.3.47: no macintosh.a file Lou Langholtz
2000-02-29 15:48 ` Lou Langholtz
2000-02-29 16:08 ` Brad Parker
2000-02-29 19:47 ` Lou Langholtz
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=38BB28DD.BE1E320E@chpc.utah.edu \
--to=ldl@chpc.utah.edu \
--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).