Re: Errors on your web page
Paul Richard Thomas wrote: They even give the impression that an open source plotting package is specific to their compiler. Incidentally, I am so wedded to DISLIN, for which the gfotran version is free, that I have never tried to build plplot; has any body tried it? Yes, I have. I help maintain parts of PLplot (notably the Fortran and Tcl bindings and the Windows platform). PLplot builds fine with gfortran (on Linux, Cygwin, MinGW) - no problem. Regards, Arjen
Re: Compiling GCC under Cygwin
Hi Angelo, true, it is not Fortran-specific. I used this mailing-list because I am familiar with it and because the purpose of this attempt was to see if I can in some way contribute other things than bug reports ;). The error you refer to is actually an error in the C source, whereas the build error I got has something to do with the Makefiles. As for the build experiment itself: - I downloaded the 4.8.1 source - I configured the Makefiles with this command: ./configure --prefix=d:/gcc-src/gcc - Then I ran make and the error message I reported before. (It is not impossible that the error is a consequence of the permission errors I got before - they are not completely gone yet, as they re-surfaced in another project.) If I understand the issue correctly, I can probably get rid of it tomorrow - as then the laptop will be connected to the proper domain. Anyway. thanks for the reaction. I will see if I can analyse it further. Regards, Arjen 2013/6/19 Angelo Graziosi : > Arjen Markus wrote: >> >> I am trying to compile GCC 4.8.1 under Cygwin. >> ../.././gcc/ada/gcc-interface/Make-lang.in:677: *** target pattern >> contains no `%'. Stop. >> make[3]: Leaving directory >> `/cygdrive/d/gcc-src/gcc-4.8.1/host-i686-pc-cygwin/gcc' >> Makefile:4160: recipe for target `all-stage1-gcc' failed >> make[2]: *** [all-stage1-gcc] Error 2 > > > > Really that doesn't seems Fortran specific.. so I CCed GCC list... > > How you configure? Usually trunk builds fine with: > > PATH_TO/configure --prefix=/usr/local/gfortran --program-suffix=-4.9 > --enable-languages=c,c++,fortran --enable-checking=release > --enable-threads=posix --enable-libgomp --enable-bootstrap > --with-arch=native --with-tune=native --with-fpmath=sse --disable-libmudflap > --disable-shared > > The only problem is this: > > http://gcc.gnu.org/ml/gcc/2013-06/msg00020.html > > but this patch > > Re: Failure bootstrapping GCC trunk on Cygwin > > seems to fix it... > > > Ciao, > Angelo.
Re: Compiling GCC under Cygwin
Hi Angelo, well, the DOS-style path only caused a warning in the configure step, so I assumed it was okay. It was not apparently. Building out-of-source is an instruction I must have missed. So, I tried again. The problem I reported before has gone, but I still get a file permission problem later on. I have not been able to solve it, even though my laptop is now connected to the domain, I have instructed the build process to use my home directory and I have set umask to - all suggestions I found or was told they might solve the problem. If anyone knows what to do about it, I would very much like to hear about it. My Google foo is failing me in unearthing a definite solution, I am afraid. Regards, Arjen 2013/6/19 Angelo Graziosi : > Ciao Arjen, > > Il 19/06/2013 21.01, Arjen Markus ha scritto: > >> >> As for the build experiment itself: >> - I downloaded the 4.8.1 source >> - I configured the Makefiles with this command: >> ./configure --prefix=d:/gcc-src/gcc > > > Hmm... Cygwin doesn't like the path in the DOS style, "d:/...". At least it > should be "/cygdrive/d/...". In any case "--prefix=PATH" is for where the > resulting GCC binaries will be installed, not where is the GCC source.. > > If I remember correctly, the build should be done in a separate directory, > > $ mkdir build_gcc > $ cd build_gcc > $ WHERE_IS/gcc-src/configure --prefix=PATH --enable-languages=c,c++,fortran > [...] > > I would suggest to follow the section "Configuration and compiling" in > > http://gcc.gnu.org/wiki/GFortranSource > > and the links therein... > > > >> If I understand the issue correctly, I can probably get rid of it >> tomorrow - as then the >> laptop will be connected to the proper domain. > > > Good luck... :) > > > Ciao, > Angelo. >
Re: Compiling GCC under Cygwin
Hi Angelo, well, contacting the Cygwin people is my next step. Regards, Arjen 2013/6/20 Angelo Graziosi : > Il 20/06/2013 12.00, Arjen Markus ha scritto: > >> So, I tried again. The problem I reported before has gone, but I still >> get a file permission problem later on. >> >> I have not been able to solve it, even though my laptop is now >> connected to the domain, I have instructed >> the build process to use my home directory and I have set umask to >> - all suggestions I found or >> was told they might solve the problem. > > > Hmm... I think that GCC can be built (out of tree) akso offline, i.e. > without any internet connection. You only need the source... > > Probably something is mis-installed or mis-configured in your system.. > > Have you tried to flag tese issues on Cygwin list? Perhaps there they have > some ideas... > > > Ciao, > Angelo. >
Re: Compiling GCC under Cygwin
Hi Jonathan, thanks - I did indeed overlook it ;). Regards, Arjen 2013/6/20 Jonathan Wakely : > On 20 June 2013 11:00, Arjen Markus wrote: >> Hi Angelo, >> >> well, the DOS-style path only caused a warning in the configure step, >> so I assumed it was okay. >> It was not apparently. Building out-of-source is an instruction I must >> have missed. > > It's documented here http://gcc.gnu.org/install/configure.html > and here http://gcc.gnu.org/wiki/FAQ#configure > and here http://gcc.gnu.org/wiki/InstallingGCC
Re: Compiling GCC under Cygwin
Hi Angelo, I found a reference to this sort of problems in the Cygwin FAQs, but this turned out to be a dead-end too. So I thought, I'd try MinGW/MSYS instead. It started off fairly well, however: - For some reason the gcc compiler did not like the /d/gcc-src/... path (from $srcdir) - it could not find the include file gmp-h.in. So I changed that to d:/gcc-src/... And that worked, until ... - the source file gen-fac.c was missing from the build directory for gmp. So I copied the various source files manually. And that worked, until ... - the assert.lo file was missing, which is necessary for libgmp. That file is nowhere in the build directory. So now I am definitely stuck. I can try to contact the Gygwin people and hope for the best. Or any of you might know the solution wrt MinGW. Regards, Arjen 2013/6/20 Arjen Markus : > Hi Angelo, > > well, contacting the Cygwin people is my next step. > > Regards, > > Arjen > > 2013/6/20 Angelo Graziosi : >> Il 20/06/2013 12.00, Arjen Markus ha scritto: >> >>> So, I tried again. The problem I reported before has gone, but I still >>> get a file permission problem later on. >>> >>> I have not been able to solve it, even though my laptop is now >>> connected to the domain, I have instructed >>> the build process to use my home directory and I have set umask to >>> - all suggestions I found or >>> was told they might solve the problem. >> >> >> Hmm... I think that GCC can be built (out of tree) akso offline, i.e. >> without any internet connection. You only need the source... >> >> Probably something is mis-installed or mis-configured in your system.. >> >> Have you tried to flag tese issues on Cygwin list? Perhaps there they have >> some ideas... >> >> >> Ciao, >> Angelo. >>
Re: Compiling GCC under Cygwin
Hi Angelo, well, after a somewhat bumpy start on the Cygwin list, I did get the information I needed. It turned out that the directories and files I had created under Windows had the permission 000 according to Cygwin, but I could still read the files and enter the directories, because the Windows permissions allowed it. However, if the build process _copied_ a file to the work directory, it inherited the 000 permission and this time it was properly translated to the equivalent Windows permissions. (At least, that is my interpretation of what was going on) I repaired the parent directory's permissions and now the build is continuing. Regards, Arjen 2013/6/20 Angelo Graziosi : > Hi Arjen, > > Il 20/06/2013 21.41, Arjen Markus ha scritto: > >> I found a reference to this sort of problems in the Cygwin FAQs, but >> this turned out to be a dead-end too. >> So I thought, I'd try MinGW/MSYS instead. >> >> It started off fairly well, however: >> >> - For some reason the gcc compiler did not like the /d/gcc-src/... >> path (from $srcdir) - it could not find the >>include file gmp-h.in. So I changed that to d:/gcc-src/... And that >> worked, until ... >> >> - the source file gen-fac.c was missing from the build directory for >> gmp. So I copied the various source files >>manually. And that worked, until ... >> >> - the assert.lo file was missing, which is necessary for libgmp. That >> file is nowhere in the build directory. >> >> So now I am definitely stuck. I can try to contact the Gygwin people >> and hope for the best. Or any of >> you might know the solution wrt MinGW. > > > I don't use MinGW.. so I can't help much.. I would suggest to contact > Cygwin/MinGW people explaining your problem/system. > > > Ciao, > Angelo. >