From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: cygwin@cygwin.com
Subject: Re: 1.7.14: Compiling GCC fails (Permission denied on mv)
Date: Wed, 11 Jul 2012 19:59:00 -0000 [thread overview]
Message-ID: <4FFDDB10.9050506@cs.utoronto.ca> (raw)
In-Reply-To: <4FFD7408.3020006@googlemail.com>
On 11/07/2012 8:39 AM, Thorolf Schulte wrote:
> Hi,
>
> this is my first mail on the mailing list, so please excuse any mistakes.
>
> I am trying to compile GCC 4.6.1 on my Cygwin 1.7.14 following this:
> http://cygwin.wikia.com/wiki/How_to_install_a_newer_version_of_GCC
>
> I downloaded and installed every package needed (GMP, MPFR,
> Multiprecision).
> Then I went into my build folder and typed
> ../gcc-4.6.1/configure --enable-languages=c,c++ --enable-libgomp
> --with-multilib-list=m64,m32 --prefix $HOME/gcc64pls --program-suffix
> -64pls
>
> (I need OMP and 64 bit support as my programs need more than 2 gb RAM!)
> That worked fine, but just for completeness, I attached the output as
> "confout.txt".
>
> Now I try to build GCC with "make -j4". Here the problem occurs: The
> data cannot be moved from "gcc" to "stage1-gcc" (Permission denied).
> After this error I checked the build folder and saw that the
> corresponding folder is not there. Then I tried to manually add all
> folders necessary, but it seems that they get deleted during build
> progress (saw some rm -r in Makefile). So I get exactly the same
> problem after manually adding all folders.
> I wanted to attach the full output as well, but the file size with
> >800kb seemed to be too big. I just attached the last 10-20%, but of
> course I can send the other output as well.
>
> Additionally, I attached my version information in "cygcheck.txt".
>
> Currently, I just dont know what to do. I tried to find some help via
> Google or the archive, but it seems that I am the only one facing this
> exact problem.
>
> Any (general) advice? Thanks!
Ignore the wikia article. Third party "advice" on how to use cygwin is
usually outdated and/or flat out wrong. The multilib thing is especially
suspicious, given that cygwin is *not* 64-bit capable.
I'd follow the directions at gcc's site, or -- even better -- invoke
`/usr/bin/gcc -v' and copy its known-good configure line. I've compiled
many versions of gcc with many versions of cygwin that way without
difficulty.
$ uname -a
CYGWIN_NT-6.1-WOW64 ryan-cms-utsc 1.7.14(0.260/5/3) 2012-04-25 09:41
i686 Cygwin
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/home/Ryan/apps/gcc-4.7/libexec/gcc/i686-pc-cygwin/4.7.0/lto-wrapper.exe
Target: i686-pc-cygwin
Configured with: ../gcc-4.7.0-src/configure
--prefix=/home/Ryan/apps/gcc-4.7 --enable-bootstrap
--enable-version-specific-runtime-libs --enable-static --enable-shared
--enable-shared-libgcc --disable-__cxa_atexit --with-dwarf2
--disable-sjlj-exceptions --enable-languages=c,c++,lto --enable-lto
Thread model: single
gcc version 4.7.0 (GCC)
Ryan
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-07-11 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 12:41 Thorolf Schulte
2012-07-11 13:03 ` Csaba Raduly
2012-07-11 13:49 ` Thorolf Schulte
2012-07-11 19:59 ` Ryan Johnson [this message]
2012-07-11 20:28 ` Thorolf Schulte
2012-07-12 2:34 ` Ryan Johnson
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=4FFDDB10.9050506@cs.utoronto.ca \
--to=ryan.johnson@cs.utoronto.ca \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).