From: "Chris du Quesnay" <duquesnay@hotmail.com>
To: linux-os@analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Building the kernel with Cygwin
Date: Thu, 25 Aug 2005 16:54:01 +0000 [thread overview]
Message-ID: <BAY14-F20DDBBC08EC1461957F455BAAB0@phx.gbl> (raw)
In-Reply-To: <Pine.LNX.4.61.0508251138220.3971@chaos.analogic.com>
Hi Dick. Thanks for your suggestion.
I tried it, however, and attempted the make again, and got the same error.
The scripts/basic directory contains a fixdep.exe after the make is run.
There is
no fixdep file. I tried renaming the fixdep.exe to fixdep, but that also
resulted in
the same make error.
Any further suggestions?
Thx,
Chris.
>From: "linux-os (Dick Johnson)" <linux-os@analogic.com>
>Reply-To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
>To: "Chris du Quesnay" <duquesnay@hotmail.com>
>CC: <linux-kernel@vger.kernel.org>
>Subject: Re: Building the kernel with Cygwin
>Date: Thu, 25 Aug 2005 11:42:46 -0400
>
>
>On Thu, 25 Aug 2005, Chris du Quesnay wrote:
>
> > Hi. I am newbie at GNU/linux.
> >
> > I am trying to build a kernel (2.6.12) for a powerpc target using
>cygwin on
> > my i686 machine. I have
> > Windows 2000 as my operating system.
> >
> > I have recent versions of cygwin (with GNU make 3.80), binutils for the
> > powerpc (gcc v 3.3.1, ld v 2.14)
> >
> > I set
> > ARCH=ppc
> > CROSS_COMPILE= powerpc-ibm-eabi-
> >
> > and I add the cross compiler/build directory to my path.
> >
> > After untaring the kernel, I issue the
> > make mrproper, which appears to work.
> >
> > Then I issue
> > make menuconfig
> >
> > and I get the following error, which I can't seem to get around:
> >
> > HOSTCC scripts/basic/fixdep
> > fixdep: no such file or directory
> > make[1]:*** [scripts/basic/fixdep] Error 2
> > make[1] Leaving directory /cygdrive/c/Linux_amcc/linux-2.6.12
> >
> >
> > Can you suggest what the problem might be? Should I be able to build
>the
> > kernel
> > with cygwin?
> >
>
>Try this temporary work-around:
>
>cd /cygdrive/c/Linux_amcc/linux-2.6.12/scripts/basic
>gcc -O2 -o fixdep fixdep.c
>
>You may also have to do the same thing for docproc, i.e.,
>gcc -O2 -o docproc docproc.c
>
>Others may tell you what's wrong, but at least this should get
>you started.
>
>
>Cheers,
>Dick Johnson
>Penguin : Linux version 2.6.12.5 on an i686 machine (5537.79 BogoMips).
>Warning : 98.36% of all statistics are fiction.
>.
>I apologize for the following. I tried to kill it with the above dot :
>
>****************************************************************
>The information transmitted in this message is confidential and may be
>privileged. Any review, retransmission, dissemination, or other use of
>this information by persons or entities other than the intended recipient
>is prohibited. If you are not the intended recipient, please notify
>Analogic Corporation immediately - by replying to this message or by
>sending an email to DeliveryErrors@analogic.com - and destroy all copies of
>this information, including any attachments, without reading or disclosing
>them.
>
>Thank you.
_________________________________________________________________
Take advantage of powerful junk e-mail filters built on patented Microsoft®
SmartScreen Technology.
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines
Start enjoying all the benefits of MSN® Premium right now and get the
first two months FREE*.
next prev parent reply other threads:[~2005-08-25 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 15:27 Chris du Quesnay
2005-08-25 15:42 ` linux-os (Dick Johnson)
2005-08-25 16:54 ` Chris du Quesnay [this message]
2005-08-25 17:05 ` linux-os (Dick Johnson)
2005-08-25 18:45 ` Christopher Faylor
2005-08-25 19:01 ` linux-os (Dick Johnson)
2005-08-27 0:45 ` Christopher Faylor
2005-08-25 17:14 ` Dmitry Torokhov
2005-08-26 11:37 vadirajcs
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=BAY14-F20DDBBC08EC1461957F455BAAB0@phx.gbl \
--to=duquesnay@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®