From: vadirajcs@eth.net
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Chris du Quesnay <duquesnay@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Building the kernel with Cygwin
Date: Fri, 26 Aug 2005 16:37:09 +0500 [thread overview]
Message-ID: <ab3079ab5860.ab5860ab3079@vsnl.net> (raw)
----- Original Message -----
From: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Date: Thursday, August 25, 2005 9:12 pm
Subject: Re: Building the kernel with Cygwin
>
> 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?
I'm not sure if this is the issue. Usually the cross compilers on MS windows
expects windows file path "c:\" where as the cygwin makefile uses unix path "/".
You can verify that with verbose output of the commmand line of your cross
compiler to see what path is been used to fetch the file fixdep.
You could try giving windows absolute path.
> >
>
> 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.
Regards,
Vadiraj
next reply other threads:[~2005-08-26 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 11:37 vadirajcs [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 15:27 Building the kernel with Cygwin Chris du Quesnay
2005-08-25 15:42 ` linux-os (Dick Johnson)
2005-08-25 16:54 ` Chris du Quesnay
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
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=ab3079ab5860.ab5860ab3079@vsnl.net \
--to=vadirajcs@eth.net \
--cc=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