public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <binutils@sourceware.org>
Subject: [RFC] 2.22 release: Compilation failure for mingw32 target with --enable-targets=all
Date: Tue, 22 Nov 2011 15:26:00 -0000	[thread overview]
Message-ID: <001201cca92b$0e9fbfe0$2bdf3fa0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <001f01cb979c$33b54080$9b1fc180$@muller@ics-cnrs.unistra.fr>

This problem is still present in binutis-2.22 sources
compilation with --enable-targets=all for mingw32 target fails
due to a warning:
gcc -DHAVE_CONFIG_H -I. -I../../binutils-2.22/ld  -I.
-I../../binutils-2.22/ld -
I../bfd -I../../binutils-2.22/ld/../bfd -I../../binutils-2.22/ld/../include
-g
-O0 -D__USE_MINGW_ACCESS -DENABLE_PLUGINS
-DLOCALEDIR="\"/usr/local/share/locale
\""  -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wno-format
-Wer
ror -g -O0 -D__USE_MINGW_ACCESS -MT eelf32_spu.o -MD -MP -MF
.deps/eelf32_spu.Tp
o -c -o eelf32_spu.o \
          -DEMBEDSPU="\"`echo embedspu | sed 's/^ld-new$/ld.bfd/;s,y,y,'`\""
eel
f32_spu.c
cc1.exe: warnings being treated as errors
eelf32_spu.c: In function 'spu_elf_relink':
eelf32_spu.c:594:3: error: passing argument 2 of 'execvp' from incompatible
poin
ter type
e:\msys\mingw32\bin\../lib/gcc/mingw32/4.5.2/../../../../include/process.h:1
20:4
2: note: expected 'const char * const*' but argument is of type 'char *
const*'
make[3]: *** [eelf32_spu.o] Error 1


From http://sourceware.org/ml/binutils/2010-12/msg00337.html
>   I got one second problem for compilation of ld
> for mingw with --enable-targets=all
> also in emultempl/spuelf.em
> about the type of execvp argument #2
> (char *const *)
> type is given line 399, but
> mingw process.h header
> gives
> (const char *const *)
> 
> which results in a warning, turned into an error
> because -Werror is the default.
> 
>   I tried to look up what the correct type should be,
> but didn't find any real unambiguous definition of that
> function.
> 
> Pierre Muller


  I got no comment on that part of the email back then, and I still don't
know if this should be considered as an error in mingw32 declarations
or if it should be fixed in Binutils sources.

 I would like to know if this warning should be corrected or not...

  To be honest, I don't understand the difference between
'const char * const *' and 'char * const *' types anyway...

Pierre Muller
GDB pascal language maintainer


  parent reply	other threads:[~2011-11-22 15:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48683.3413750448$1288971470@news.gmane.org>
2010-11-05 17:21 ` [OBV/RFA] Fix compilation of ld/emultempl/spuelf.em on systems where HAVE_MKSTEMP is not defined Richard Sandiford
2010-12-09 11:11   ` Not in 2.21 sources... " Pierre Muller
2010-12-09 11:20     ` Tristan Gingold
2010-12-09 12:26       ` Pierre Muller
2010-12-10 10:45         ` Tristan Gingold
2011-11-22 15:26         ` Pierre Muller [this message]
2011-11-25 16:40           ` [RFC] 2.22 release: Compilation failure for mingw32 target with --enable-targets=all nick clifton
2011-11-25 17:02             ` Pedro Alves
2011-11-29 12:43               ` nick clifton
2011-11-29 12:53                 ` Alan Modra
2011-11-29 16:27                   ` nick clifton
2011-11-30 11:52                     ` Alan Modra
2011-12-01 11:39                       ` nick clifton
2011-11-26 11:18             ` JonY

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='001201cca92b$0e9fbfe0$2bdf3fa0$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=binutils@sourceware.org \
    /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).