Re: Compilation error with GCC
Thanks a lot Jouke, Pete, Dmitry and Paul The patches did indeed fix the problem. I also checked from the latest Git commit (d365bdfdbc925d) in a clean clone, which indeed worked smoothly! Thanks for the very prompt replies and action! Very impressive! Thanks again, Mohammad On 12/19/21 20:04, Jouke Witteveen wrote: I believe what you are seeing is reported here: https://savannah.gnu.org/bugs/?60798 The patches "file #52422" and "file #52428" should resolve your issues. Regards, - Jouke On Sun, Dec 19, 2021 at 7:55 PM Mohammad Akhlaghi wrote: So sorry, there was a typo in my last mail: As the previously attached file shows, I was built Make over commit 'e62f4cf9a2eaf7' (Sun Nov 28 14:17:55 2021 -0500). Cheers, Mohammad On 12/19/21 19:49, Mohammad Akhlaghi wrote: Dear GNU Make maintainers, I just cloned Make (with the 'master' branch on commit c5d4b7b2f260c) and bootstrapped it with Gnulib (on commit 64f5221ef20ba) on Arch GNU/Linux and with GCC 11.1.0 and Glibc 2.33. The configuration went nicely, however, during the compilation it crashed with the attached error. Please let me know if any further information is necessary. Thank you, Mohammad
Re: Compilation error with GCC
On Sun, 2021-12-19 at 20:04 +0100, Jouke Witteveen wrote: > The patches "file #52422" and "file #52428" should resolve your > issues. I pushed these changes to Git.
Re: Compilation error with GCC
Jouke is the MVP on response time! On Sun, Dec 19, 2021 at 8:05 PM Jouke Witteveen wrote: > I believe what you are seeing is reported here: > https://savannah.gnu.org/bugs/?60798 > > The patches "file #52422" and "file #52428" should resolve your issues. > > Regards, > - Jouke > > On Sun, Dec 19, 2021 at 7:55 PM Mohammad Akhlaghi > wrote: > > > > So sorry, there was a typo in my last mail: > > > > As the previously attached file shows, I was built Make over commit > > 'e62f4cf9a2eaf7' (Sun Nov 28 14:17:55 2021 -0500). > > > > Cheers, > > Mohammad > > > > On 12/19/21 19:49, Mohammad Akhlaghi wrote: > > > Dear GNU Make maintainers, > > > > > > I just cloned Make (with the 'master' branch on commit c5d4b7b2f260c) > > > and bootstrapped it with Gnulib (on commit 64f5221ef20ba) on Arch > > > GNU/Linux and with GCC 11.1.0 and Glibc 2.33. > > > > > > The configuration went nicely, however, during the compilation it > > > crashed with the attached error. > > > > > > Please let me know if any further information is necessary. > > > > > > Thank you, > > > Mohammad > > > > > > >
Re: Compilation error with GCC
On Sun, Dec 19, 2021 at 1:51 PM Mohammad Akhlaghi wrote: > The configuration went nicely, however, during the compilation it > crashed with the attached error. i think, Jouke provided patches to workaround this warning. You can pass a flag to gcc to not treat warnings as errors. e.g. $ make CFLAGS=-Wno-error regards, Dmitry
Re: Compilation error with GCC
I believe what you are seeing is reported here: https://savannah.gnu.org/bugs/?60798 The patches "file #52422" and "file #52428" should resolve your issues. Regards, - Jouke On Sun, Dec 19, 2021 at 7:55 PM Mohammad Akhlaghi wrote: > > So sorry, there was a typo in my last mail: > > As the previously attached file shows, I was built Make over commit > 'e62f4cf9a2eaf7' (Sun Nov 28 14:17:55 2021 -0500). > > Cheers, > Mohammad > > On 12/19/21 19:49, Mohammad Akhlaghi wrote: > > Dear GNU Make maintainers, > > > > I just cloned Make (with the 'master' branch on commit c5d4b7b2f260c) > > and bootstrapped it with Gnulib (on commit 64f5221ef20ba) on Arch > > GNU/Linux and with GCC 11.1.0 and Glibc 2.33. > > > > The configuration went nicely, however, during the compilation it > > crashed with the attached error. > > > > Please let me know if any further information is necessary. > > > > Thank you, > > Mohammad > > >
Re: Compilation error with GCC
So sorry, there was a typo in my last mail: As the previously attached file shows, I was built Make over commit 'e62f4cf9a2eaf7' (Sun Nov 28 14:17:55 2021 -0500). Cheers, Mohammad On 12/19/21 19:49, Mohammad Akhlaghi wrote: Dear GNU Make maintainers, I just cloned Make (with the 'master' branch on commit c5d4b7b2f260c) and bootstrapped it with Gnulib (on commit 64f5221ef20ba) on Arch GNU/Linux and with GCC 11.1.0 and Glibc 2.33. The configuration went nicely, however, during the compilation it crashed with the attached error. Please let me know if any further information is necessary. Thank you, Mohammad
Re: Compilation error on master branch (Commit c5d4b7b)
On 10/3/21 23:38, Paul Smith wrote: On Sun, 2021-10-03 at 23:23 +0200, Mohammad Akhlaghi wrote: I then ran the standard './configure' and 'make' commands to build it, but the build failed with the attached error messages when building 'src/guile.c'. These errors appear to be coming from compiling src/read.c, not src/guile.c. You are right! I had initially ran 'make' in parallel so the proper compile command wasn't on top of the error message. To be more clear, I just ran these commands to generate the full log that is attached: make clean make -k &> build-log-c5d4b7b2f.txt gzip --best build-log-c5d4b7b2f.txt This shows that this error also occurs in 'src/main.c'. I'd be happy to try the build after you look into it and make a correction commit (in any branch). Cheers, Mohammad build-log-c5d4b7b2f.txt.gz Description: application/gzip
Re: Compilation error on master branch (Commit c5d4b7b)
On Sun, 2021-10-03 at 23:23 +0200, Mohammad Akhlaghi wrote: > I then ran the standard './configure' and 'make' commands to build > it, but the build failed with the attached error messages when > building 'src/guile.c'. These errors appear to be coming from compiling src/read.c, not src/guile.c. I strongly suspect these are false-positive warnings but I'll take a look.
Re: Compilation error
On Tue, 2008-05-13 at 16:02 +, willard mapurisa wrote: I get the following compilation error when I try to compile a nurbs++ package with openGL support . Hi Willard; This mailing list is for people having problems with the program GNU make. Your error here is not related to make, it's related to your system (not having the correct libraries installed) or your compiler (not being able to find them) or the software you're trying to build (not allowing you to specify where they are). Please ask on mailing lists dedicated to those areas; you will find more help there. Good luck! ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
Re: Compilation error on OpenSteep 4.0
Hello, I am running make v. 3.77 and cc(gcc) v. 2.58. On Mon, 13 Mar 2000, Paul D. Smith wrote: %% "Francisco A. Tomei Torres" [EMAIL PROTECTED] writes: fatt cc -DHAVE_CONFIG_H -I. -I. -I.. -I./glob -g -O2 -c glob.c fatt ./glob.h:51: undefined type, found `__SIZE_TYPE__' I'll need more info than this. I'm pretty sure it's some kind of local configuration error. First, what version of GNU make are you working with? That line (glob.h:51) is only supposed to be compiled if you're using GCC and the version of GCC is 2.x: # if defined __GNUC__ __GNUC__ = 2 typedef __SIZE_TYPE__ __size_t; # else So, we'll have to assume that your "cc" is really GCC. What version of GCC is it? Use "cc --version". Next, why isn't __SIZE_TYPE__ defined? AFAIK all versions of GCC define this in, for example, stddef.h. Does yours? If that all seems to check out, you should run that compile line by hand with the -v option and check that there aren't any other odd include directories that get passed to the compiler. Then, you should run it with the -E output and see if you can tell why __SIZE_TYPE__ isn't defined where it should be. -- --- Paul D. Smith [EMAIL PROTECTED] Network Management Development "Please remain calm...I may be mad, but I am a professional." --Mad Scientist --- These are my opinions---Nortel Networks takes no responsibility for them.
