public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Eshan Dhawan <eshandhawan51@gmail.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: joel@rtems.org, newlib@sourceware.org
Subject: Re: [PATCH 0/1] Hard-float fenv support for PowerPc
Date: Fri, 5 Jun 2020 21:18:06 +0530	[thread overview]
Message-ID: <7B87FE16-601A-4037-846B-3206434C8EE6@gmail.com> (raw)
In-Reply-To: <a94e8237-5e3f-a64e-3ada-3b89f0ffe724@embedded-brains.de>

Hi Sebastian, 

Did you run autoreconf -fvi in newlib directory.
This patch only contains the hand written files
No files generated by autoconf are included in this patch 
Are those files required to be included ?? 

> On 05-Jun-2020, at 6:16 PM, Sebastian Huber <sebastian.huber@embedded-brains.de> wrote:
> 
> Hello,
> 
> this patch breaks the powerpc-rtems build:
> 
> gmake[8]: Leaving directory '/usr/home/user/rtems-source-builder/rtems/build/powerpc-rtems6-gcc-6ea6c49-newlib-e6ce6f1-x86_64-freebsd12.1-1/build/powerpc-rtems6/m403/newlib/libm/fenv'
> Making all in machine
> gmake[8]: Entering directory '/usr/home/user/rtems-source-builder/rtems/build/powerpc-rtems6-gcc-6ea6c49-newlib-e6ce6f1-x86_64-freebsd12.1-1/build/powerpc-rtems6/m403/newlib/libm/machine'
> Making all in powerpc
> cd: powerpc: No such file or directory
> 
> How did you test your patch?


  reply	other threads:[~2020-06-05 15:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 16:41 Eshan dhawan
2020-06-02 16:41 ` [PATCH 1/1] hard float support for PowerPC taken from FreeBSD Eshan dhawan
2020-06-03  9:19   ` Corinna Vinschen
2020-06-05 21:41     ` Joel Sherrill
2020-06-05 12:46 ` [PATCH 0/1] Hard-float fenv support for PowerPc Sebastian Huber
2020-06-05 15:48   ` Eshan Dhawan [this message]
2020-06-07 13:39     ` Sebastian Huber

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=7B87FE16-601A-4037-846B-3206434C8EE6@gmail.com \
    --to=eshandhawan51@gmail.com \
    --cc=joel@rtems.org \
    --cc=newlib@sourceware.org \
    --cc=sebastian.huber@embedded-brains.de \
    /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).