X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Leo Liu Subject: Re: something goes wrong while compiling linux kernel under cygwin Date: Mon, 18 Dec 2006 05:37:25 +0000 (UTC) Lines: 109 Message-ID: References: <89c3ea2b0612160820p32fb7295qb50b35b17cab89af AT mail DOT gmail DOT com> <89c3ea2b0612170720n64d69a9fv50accb82149e25bf AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com andy wang gmail.com> writes: > > > > > But there is a little issue when i'm using command: > > "mount -o cygexec -o managed /cygdrive/d/testdir1 /testdir2". > "man mount" you can see the help the mount. you can always find some > answers if you try "man your-command". > The first path is Windows path and second is the POSIX path. so using: > mount -u -o managed "e:\test\dir1" /tmp/dir1 > > if you want to umount, try "umount -u /tmp/dir1" but notice if you > umount a managed dir which contains the files, you must remount it > with "-f" option! > > > > > Actually, i just need to compile linux kernel on x86 arch. So if the case- > > sensitive problem is solved, can it fix my original problem? > > > Your oringal problem can be solved by install cross-compiler not the > cygwin managed tips. > > > Sorry for my limited knowledge, but i really need this for work. > > > But if you do not totally understand the process and do not study > carefully about the cross-compiler It will be full of pains I think > > > If you read the post carefully, your solution will be crosstool-0.43, > and if you try that first, you don't even need to try "-o managed" > option on cygwin! > > Good luck for the kernel adventure on cygwin > > Regards, > Andy > > Hi Andy, You are right. You make me know the key to my problem and lead me to a right way to solve the issue. Thanks for your warm-heartedness. You are my hero. ;) Now,I have turned to cross-tool to solve my problem, and I have run demo- i686.sh and mkdir as its tips. At the beginning of re-compiling all toolchains needed, everything goes fine, but a make problem occured during the process. I'm not sure if it is a bug of cross-tool or cause of my wrong settings. I have a snapshot for you, can you check into it for me? And then i will look for the solution. the weblink of my snapshot: http://desfilms.googlepages.com/make_error.jpg below is my demo-i686.sh(i didn't uncommet the #, just used default gcc version): ----------------------------------------------------------- #!/bin/sh # This script has one line for each known working toolchain # for this architecture. Uncomment the one you want. # Generated by generate-demo.pl from buildlogs/all.dats.txt set -ex TARBALLS_DIR=$HOME/downloads RESULT_TOP=/opt/crosstool export TARBALLS_DIR RESULT_TOP GCC_LANGUAGES="c,c++" export GCC_LANGUAGES # Really, you should do the mkdir before running this, # and chown /opt/crosstool to yourself so you don't need to run as root. mkdir -p $RESULT_TOP #eval `cat i686.dat gcc-2.95.3-glibc-2.1.3.dat` sh all.sh --notest #eval `cat i686.dat gcc-2.95.3-glibc-2.2.2.dat` sh all.sh --notest #eval `cat i686.dat gcc-2.95.3-glibc-2.2.5.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.2.3-glibc-2.2.5.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.2.3-glibc-2.3.2.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.3.6-glibc-2.1.3.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.3.6-glibc-2.2.2.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.3.6-glibc-2.2.5.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.3.6-glibc-2.3.2.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.3.6-glibc-2.3.5.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.3.6-glibc-2.3.5-tls.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.3.6-glibc-2.3.6.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.3.6-glibc-2.3.6-tls.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.4.5-glibc-2.2.2.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.4.5-glibc-2.2.5.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.4.5-glibc-2.3.2.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.4.5-glibc-2.3.5.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.4.5-glibc-2.3.5-tls.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.4.5-glibc-2.3.6.dat` sh all.sh --notest #eval `cat i686.dat gcc-3.4.5-glibc-2.3.6-tls.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.0.2-glibc-2.2.2.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.0.2-glibc-2.3.2.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.0.2-glibc-2.3.5.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.0.2-glibc-2.3.5-tls.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.0.2-glibc-2.3.6.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.0.2-glibc-2.3.6-tls.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.1.0-glibc-2.2.2.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.1.0-glibc-2.3.2.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.1.0-glibc-2.3.5.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.1.0-glibc-2.3.5-tls.dat` sh all.sh --notest #eval `cat i686.dat gcc-4.1.0-glibc-2.3.6.dat` sh all.sh --notest eval `cat i686.dat gcc-4.1.0-glibc-2.3.6-tls.dat` sh all.sh --notest echo Done. ----------------------------------------------------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/