linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Lou Langholtz <ldl@chpc.utah.edu>
To: Brad Parker <brad@parker.boston.ma.us>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: problem building 2.3.47: no macintosh.a file
Date: Tue, 29 Feb 2000 12:47:41 -0700	[thread overview]
Message-ID: <38BC225D.69570BE3@chpc.utah.edu> (raw)
In-Reply-To: 200002291608.LAA16958@p2.parker.boston.ma.us


Brad Parker wrote:

> I've gotten 2.3.47 from kernel.org to build, doing pretty much what
> Lou did (below).  To get rid of the link errors you need to edit
> arch/ppc/kernel/ppc_ksyms.c and comment out the line with "strspn" in
> it.
>
> It boots on my imac.  I don't have a lot of milage yet, but usb works :-)
> fyi - I plan to switch to an rsync from Paul's tree...
>
> -brad
>
> >. . . Argh! I've gotten now to the point that 2.3.47 builds all the way then
> the linker
> >barfs with two "multiple definition of" errors.  . . .
> >kernel/kernel.o(.kstrtab+0x1f44): multiple definition of `__kstrtab_strspn'
> >arch/ppc/kernel/kernel.o(.kstrtab+0x4a4): first defined here
> >kernel/kernel.o(__ksymtab+0x9e0): multiple definition of `__ksymtab_strspn'
> >arch/ppc/kernel/kernel.o(__ksymtab+0x178): first defined here
> >make: *** [vmlinux] Error 1
> >
> >Can anyone help me with these definition errors? . . .

That was it!!! I'm so excited! I'm running kernel.org's 2.3.47 now on my PowerMac
7500 and haven't encountered a bug yet. Network I/O through my PPP connection even
feels a little snappier now. With any luck -- as people have indicated -- I won't
have anymore PPP freeze ups either.

Rambling BTW (for the linuxppc-dev archives mostly):

I did encounter some trouble  with getting PPP to install properly. First
I reliazed I had to update my pppd (etc) which fortunately I had sources for
already on my system. Then I found I had to set CONFIG_PPP_ASYNC=m in my .config
and run "make modules; make modules_install" to make the kernel happy. Trying to
build it within the kernel (instead of as a module), didn't seem to want to let
PPP work. modprobe kept complaining in my syslog file that it couldn't locate
module "tty-ldisc-3" which the PPP source dist says should be aliased if it's
built as a module to the ppp_async module (in the /etc/modules.conf file). So
after building and installing ppp_async as a module and updating the modules conf
file PPP was able to work. Is this a bug in "make xconfig" where it should limit
the choices to either "m" or "n"? Or maybe something I did wrong? I guess so long
as my system can still reboot I won't loose any more sleep over it :-)


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-02-29 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2000-02-29 16:19     ` Where to get Paul's tree [was Re: problem building 2.3.47: no macintosh.a file] phandel
2000-02-29  1:19 problem building 2.3.47: no macintosh.a file Lou Langholtz
2000-02-29  2:03 ` 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=38BC225D.69570BE3@chpc.utah.edu \
    --to=ldl@chpc.utah.edu \
    --cc=brad@parker.boston.ma.us \
    --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).