public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel@rtems.org>
To: Newlib <newlib@sourceware.org>
Subject: RTEMS Tools Build with Recent Newlib
Date: Mon, 31 Jan 2022 08:36:24 -0600	[thread overview]
Message-ID: <CAF9ehCXrJeF0GY7zyHs55HWEXy5-q4_7oYddeDeJ+eQeqxHcog@mail.gmail.com> (raw)

Hi

I bumped the newlib hash to the following in the RTEMS tools recipes:

commit 502cf4b7b5b79b83e8f41b4074212f9e27753f0b (HEAD -> master,
origin/master, origin/HEAD)
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Sat Jan 29 01:33:44 2022 -0500

    libgloss: fix more missing dir with parallel install

    Depending on the processing order of rules when installing in parallel,
    these install rules might be processed before some other rule happens
    to create the respective dirs.  Make sure each one creates the needed
    dirs before installing into them.

And tried to build the following architectures:

aarch64 arm bfin i386 lm32 m68k microblaze mips moxie nios2 or1k
powerpc riscv sh sparc64 sparc v850 x86_64

arm, i386, and riscv did not complete the tool chain build.

All three architectures failed with multiple files having errors like these:

In file included from
../../../../../../gnu-mirror-gcc-40ccb47/newlib/libm/machine/arm/s_floor.c:39:
../../../../../../gnu-mirror-gcc-40ccb47/newlib/libm/machine/arm/../../math/s_floor.c:65:10:
fatal error: fdlibm.h: No such file or directory
   65 | #include "fdlibm.h"
      |          ^~~~~~~~~~
compilation terminated.
make[5]: *** [lib_a-s_floor.o] Error 1
../../../../../../gnu-mirror-gcc-40ccb47/newlib/libm/machine/arm/s_fma_arm.c:37:10:
fatal error: math_config.h: No such file or directory
   37 | #include "math_config.h"
      |          ^~~~~~~~~~~~~~~

I didn't proceed with building RTEMS or our tests but will once all
tool chains are building.

--joel

             reply	other threads:[~2022-01-31 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 14:36 Joel Sherrill [this message]
2022-02-01  3:28 ` 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:
  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=CAF9ehCXrJeF0GY7zyHs55HWEXy5-q4_7oYddeDeJ+eQeqxHcog@mail.gmail.com \
    --to=joel@rtems.org \
    --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).