public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Gedare Bloom <gedare@rtems.org>
To: aditya upadhyay <aadit0402@gmail.com>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>,
	Joel Sherrill <joel@rtems.org>
Subject: Re: Work on newlib
Date: Tue, 16 May 2017 15:53:00 -0000	[thread overview]
Message-ID: <CAC82fA2rO71bitv_UQ7gJqfreejYOs_j+qOMLn6X+P=o4uNEfw@mail.gmail.com> (raw)
In-Reply-To: <CAMZxAxcdi5RX7PDOKU25aQKghG2DAPFHD4QSyd6vik_T=nOgMQ@mail.gmail.com>

On Tue, May 16, 2017 at 2:56 AM, aditya upadhyay <aadit0402@gmail.com> wrote:
> Hello Developers,
>
> I am Aditya Upadhyay got selected in Google Summer of Code(2017) for RTEMS
> organization. My Proposal has been accepted for POSIX Compliance, Where I
> have to work on newlib and some libraries that is not in RTEMS, have to
> implement.
>
> I am having a j-newlib script pointed by Joel Sherrill, I have used this
> script using following command :
>  aditya@aditya-Lenovo-ideapad-110-15ACL:~/development/newlib$ ./j-newlib
> These are the targets in j-newlib :
>  # primary targets
>   TARGETS="${TARGETS} sparc-rtems4.12"
>   TARGETS="${TARGETS} arm-rtems4.12"
>   TARGETS="${TARGETS} powerpc-rtems4.12"
>   TARGETS="${TARGETS} mips-rtems4.12"
>   TARGETS="${TARGETS} i386-rtems4.12"
>   TARGETS="${TARGETS} m68k-rtems4.12"
>
> There are some secondary and optimistic targets.
>
> and generated directory like b-sparc64-rtems4.12-newlib,
> b-sparc-rtems4.12-newlib, b-arm-rtems4.12-newlib etc..but there is not a
> single .exe file after i fired make command.
>
> I do not know whether i am going in right working direction or not ?
> Please correct me. Any direction or suggestion will be greatly appreciable.
>
Without knowing what this j-newlib script does, it is hard to help you
interpret the output. Perhaps Joel can help you. For RTEMS, you should
compile newlib as part of building gcc. This means if you have
modified newlib you should re-compile gcc with it, and then you would
re-compile RTEMS and run its testsuite in order to test your changes.

To compile a modified newlib into the gcc toolchain, you should
consider creating a patch of your change to newlib (e.g. from
git-format-patch) and add the patch to your local rtems-source-builder
in order to apply a custom patch during the compiler re-build. See
https://docs.rtems.org/branches/master/rsb.html#patches for some
documentation on how you do this, which includes an example
specifically related to patching newlib.

Gedare

> Thanks & Best Regards,
> Aditya Upadhyay

       reply	other threads:[~2017-05-16 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMZxAxcdi5RX7PDOKU25aQKghG2DAPFHD4QSyd6vik_T=nOgMQ@mail.gmail.com>
2017-05-16 15:53 ` Gedare Bloom [this message]
2017-05-16 16:12   ` Joel Sherrill

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='CAC82fA2rO71bitv_UQ7gJqfreejYOs_j+qOMLn6X+P=o4uNEfw@mail.gmail.com' \
    --to=gedare@rtems.org \
    --cc=aadit0402@gmail.com \
    --cc=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).