All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Vier <nester@erols.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: Franz Sirl <Franz.Sirl@munich.netsurf.de>,
	mklinux-development-system@public.lists.apple.com,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: egcs-1.1.1-1c bug (was Re: major ksyms problem)
Date: Wed, 24 Feb 1999 13:40:19 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.05.9902241335420.6173-100000@localhost.erols.com> (raw)
In-Reply-To: <99022322220600.00836@ns1102.munich.netsurf.de>


On Tue, 23 Feb 1999, Franz Sirl wrote:

> >it is an egcs bug. egcs-1.1.1-1c failss to build working bsd_comp.o,
> >ppp_deflate.o, and hfs.o; egcs-1.0-2e.ppc.rpm builds it perfectly. i'm
> >getting a newer build of egcs right now, to see if it's fixed.
> 
> What is the problem with these modules? Give a better description on what you
> mean with "working"? They work perfectly for me with a self-compiled 2.2.1
> kernel, and I compiled working modules with multiple kernel versions
> since the 
> egcs-1.1 alpha phase.
> If your only problem is the "unhandled relocation type", install a newer
> modutils package (>=2.1.121), that will fix it.

yup, that fixed it. 8) i wonder what changed in egcs between 1.0 and
1.1.1 that makes the problem arise.

--
Tom Vier - 0x82B007A8
thomass@erols.com        | goto the Zero Page at:
Tortured Souls Software  | http://www.erols.com/thomassr/zero/


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  parent reply	other threads:[~1999-02-24 18:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.05.9902220432430.2138-100000@localhost.erols.com>
1999-02-22 14:36 ` egcs-1.1.1-1c bug (was Re: major ksyms problem) Tom Vier
1999-02-23  7:22   ` Gary Thomas
1999-02-23 12:24     ` Tom Vier
1999-02-23 20:53       ` Tom Vier
     [not found] ` <Pine.LNX.4.05.9902220928100.405-100000@localhost.erols.com >
1999-02-23 15:00   ` Franz Sirl
1999-02-23 21:06     ` Tom Vier
1999-02-23 21:15       ` Franz Sirl
1999-02-24  9:53         ` Gary Thomas
1999-02-24 16:06           ` Franz Sirl
1999-02-25  2:20           ` Tom Vier
1999-02-24 18:40         ` Tom Vier [this message]
1999-02-24  7:14       ` Michel Lanners

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=Pine.LNX.4.05.9902241335420.6173-100000@localhost.erols.com \
    --to=nester@erols.com \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=Franz.Sirl@munich.netsurf.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mklinux-development-system@public.lists.apple.com \
    --cc=thomassr@erols.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.