public inbox for
 help / color / mirror / Atom feed
From: "Helmer, Steven" <>
To: "" <>
Subject: List of bugs in newlib-4.3.0 release
Date: Wed, 13 Sep 2023 19:03:50 +0000	[thread overview]
Message-ID: <SA1P110MB13608D4721A3D23228ACF0EF8DF0A@SA1P110MB1360.NAMP110.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]

I encountered a few bugs (compilation and others) in the newlib- release. Compiling using GCC version 12.2.0 for FreeRTOS and an in-house processor.

  1.  The function declaration for mcwidth in newlib/libc/string/wcwidth.c does not match the prototype in newlib/libc/include/wchar.h .

  1.  Should be including sys/types.h not sys/_types.h  in newlib/libc/include/stdio.h

  1.  In order to build boost and some other third party libraries, need to have the following defined in newlib/libc/include/glob.h

#define GLOB_NOMATCH    (-3)    /* No matches found.  */
#define GLOB_NOSYS      (-4)    /* Not implemented.  */
/* Previous versions of this file defined GLOB_ABEND instead of
 *    GLOB_ABORTED.  Provide a compatibility definition here.  */

  1.  In newlib/libc/locale/locale.c need to add

  int ret = 0;
inside the first #else clause in function __loadlocale . This is after the #ifdef __CYGWIN__ line.

  1.  The return type for pthread_yield should be int not void in newlib/libc/include/pthread.h.  This matches both Linux and FreeRTOSLabs posix threads.

Arcfield Proprietary E-MAIL CONTENT CLASSIFICATION NOTICE CONFIDENTIAL AND/OR PROPRIETARY INFORMATION OF ARCFIELD. This e-mail message and/or its attachment contains confidential and/or proprietary information of Arcfield that may only be received, disclosed, or used as authorized by Arcfield. The information in this message may be exempt from release under the Freedom of Information Act. If you received this message in error, please delete all copies and promptly notify the sender.

             reply	other threads:[~2023-09-13 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 19:03 Helmer, Steven [this message]
2023-10-15  6:29 ` Mike Frysinger

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SA1P110MB13608D4721A3D23228ACF0EF8DF0A@SA1P110MB1360.NAMP110.PROD.OUTLOOK.COM \ \ \

* 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).