From: vanamali gouripeddi <mail2gvs@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: 8260 PQ2FADS
Date: Fri, 7 Oct 2005 12:47:30 +0530 [thread overview]
Message-ID: <ebbd6cda0510070017h435922e6k1c44f3725ce3c99e@mail.gmail.com> (raw)
hi
after the configuration and installation of binutils-2.16.1 i hav
added headers in the same tools directory now as iam trying to
configure gcc-2.95.3 the following error is displayed after the make
command
-mppc not identified
libcc2.a as one error and
stmp-multilib-sub
as the other plz provide the solution as we running out of time
On 10/7/05, linuxppc-embedded-request@ozlabs.org
<linuxppc-embedded-request@ozlabs.org> wrote:
> Send Linuxppc-embedded mailing list submissions to
> =09linuxppc-embedded@ozlabs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> =09https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> or, via email, send a message with subject or body 'help' to
> =09linuxppc-embedded-request@ozlabs.org
>
> You can reach the person managing the list at
> =09linuxppc-embedded-owner@ozlabs.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linuxppc-embedded digest..."
>
>
> Today's Topics:
>
> 1. mpc8272ads support in linux-2.4 (Alex Zeffertt)
> 2. TKO Notice: ***Urgent Safeharbor Department Notice***
> (aw-confirm@eBay.com)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 6 Oct 2005 17:36:27 +0100
> From: Alex Zeffertt <ajz@cambridgebroadband.com>
> Subject: mpc8272ads support in linux-2.4
> To: linuxppc-embedded@ozlabs.org
> Message-ID: <20051006173628.53f25862.ajz@cambridgebroadband.com>
> Content-Type: text/plain; charset=3DUS-ASCII
>
> Hi list,
>
> I have read that the MPC8272ADS board is supported in linux-2.6. Has
> anybody backported this support to linux-2.4. I am using linux-2.4.25
> from ELDK. If anyone has a patch I would be very grateful if they
> sent it to me.
>
> Regards,
>
> Alex Zeffertt
>
> PS Does anyone know where the master PPC patches are kept? I.e. the
> ones you apply to kernels from kernel.org to get all the stuff that
> hasn't yet been upstreamed.
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 6 Oct 2005 16:57:36 -0400 (EDT)
> From: aw-confirm@eBay.com <aw-confirm@eBay.com>
> Subject: TKO Notice: ***Urgent Safeharbor Department Notice***
> To: linuxppc-embedded@ozlabs.org
> Message-ID: <20051006205736.38DA586FEE6@athens.9degrees.com>
> Content-Type: text/plain; charset=3D"us-ascii"
>
> An HTML attachment was scrubbed...
> URL:
> http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20051006/af0ff7=
7a/attachment-0001.htm
>
> ------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
> End of Linuxppc-embedded Digest, Vol 14, Issue 10
> *************************************************
>
reply other threads:[~2005-10-07 7:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ebbd6cda0510070017h435922e6k1c44f3725ce3c99e@mail.gmail.com \
--to=mail2gvs@gmail.com \
--cc=linuxppc-embedded@ozlabs.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).