From: Carlos O'Donell <carlos@redhat.com>
To: Fangrui Song <i@maskray.me>, libc-help@sourceware.org
Subject: Re: Lightning talk notes on glibc
Date: Wed, 20 Jan 2021 11:25:42 -0500 [thread overview]
Message-ID: <75598397-3660-60c0-818a-936aabf3679f@redhat.com> (raw)
In-Reply-To: <20210120074815.k6km6cmhrt4aknpo@gmail.com>
On 1/20/21 2:48 AM, Fangrui Song wrote:
> During development, some interesting targets:
>
> ((((((It'd be nice to list more targets here))))))))
> ```sh
> make -C Debug lib # meaning?
> make -C Debug objs # meaning?
> make -C Debug others # meaning?
> make -C Debug check-abi
> ```
Note 'make help' which should be updated to list useful
targets that developer want to use.
Note debugglibc.sh for debugging test and attaching to tests
that run in containers.
Lastly 'make test' with options to run one test (which usually
works depending on the kind of test to execute).
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-01-20 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 7:48 Fangrui Song
2021-01-20 16:17 ` Adhemerval Zanella
2021-01-20 16:20 ` Carlos O'Donell
2021-01-20 16:25 ` Carlos O'Donell [this message]
2021-01-20 16:25 ` Carlos O'Donell
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=75598397-3660-60c0-818a-936aabf3679f@redhat.com \
--to=carlos@redhat.com \
--cc=i@maskray.me \
--cc=libc-help@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).