public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Jennifer Averett <Jennifer.Averett@OARcorp.com>
To: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: warning question
Date: Thu, 20 Apr 2023 14:44:54 +0000	[thread overview]
Message-ID: <BN6PR19MB00981B71FFC0ECBC2F7C985D9B639@BN6PR19MB0098.namprd19.prod.outlook.com> (raw)

I get the warning listed below when building with the config options:

   --enable-newlib-iconv-encodings=big5,cp775,cp850,cp852,cp855,\
cp866,euc_jp,euc_kr,euc_tw,iso_8859_1,iso_8859_10,iso_8859_11,\
iso_8859_13,iso_8859_14,iso_8859_15,iso_8859_2,iso_8859_3,\
iso_8859_4,iso_8859_5,iso_8859_6,iso_8859_7,iso_8859_8,iso_8859_9,\
iso_ir_111,koi8_r,koi8_ru,koi8_u,koi8_uni,ucs_2,ucs_2_internal,\
ucs_2be,ucs_2le,ucs_4,ucs_4_internal,ucs_4be,ucs_4le,us_ascii,\
utf_16,utf_16be,utf_16le,utf_8,win_1250,win_1251,win_1252,\
win_1253,win_1254,win_1255,win_1256,win_1257,win_1258\
    --enable-newlib-reent-thread-local \
    --enable-newlib-io-c99-formats \
    --enable-threads \
    --target= aarch64-rtems6\

  CC       libc/stdio/libc_a-vdprintf.o
../../../newlib-cygwin/newlib/libc/stdio/tmpnam.c: In function '_tmpnam_r':
../../../newlib-cygwin/newlib/libc/stdio/tmpnam.c:135:14: warning: assignment to 'char *' from 'char' makes pointer from integer without a cast [-Wint-conversion]
  135 |       result = _REENT_EMERGENCY(p);
      |              ^

  CC       libc/signal/libc_a-psignal.o
../../../../newlib-cygwin/newlib/libc/stdio/tmpnam.c: In function '_tmpnam_r':
../../../../newlib-cygwin/newlib/libc/stdio/tmpnam.c:135:14: warning: assignment to 'char *' from 'char' makes pointer from integer without a cast [-Wint-conversion]
  135 |       result = _REENT_EMERGENCY(p);
      |              ^


Just wanted to know if this was a known issue.

Thanks
Jennifer Averett


             reply	other threads:[~2023-04-20 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 14:44 Jennifer Averett [this message]
2023-04-20 15:12 ` Jeff Johnston

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=BN6PR19MB00981B71FFC0ECBC2F7C985D9B639@BN6PR19MB0098.namprd19.prod.outlook.com \
    --to=jennifer.averett@oarcorp.com \
    --cc=newlib@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).