From: the <the.guard@mail.ru>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc-2.27 is broken
Date: Tue, 30 Oct 2018 13:02:28 -0600 [thread overview]
Message-ID: <7b1501d0-25ae-411a-216a-a32a36ddb6a5@mail.ru> (raw)
In-Reply-To: <20181030185241.GG1931@ca.inter.net>
On 10/30/2018 12:52 PM, Philip Webb wrote:
> NB above : the error you cite is '4' :
> this shows there are other errors '1' '2' '3' above, which are more important.
> It would help if you find them & report them to the list.
Thanks, but that's the whole gcc output I got.
BTW the code for this is:
$ cat main.c
#include <stdio.h>
int main(int argc, char **argv) {
printf("hello world\n");
return 0;
}
next prev parent reply other threads:[~2018-10-30 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 18:27 [gentoo-user] glibc-2.27 is broken the
2018-10-30 18:52 ` Philip Webb
2018-10-30 19:02 ` the [this message]
2018-11-01 0:12 ` Andrew Savchenko
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=7b1501d0-25ae-411a-216a-a32a36ddb6a5@mail.ru \
--to=the.guard@mail.ru \
--cc=gentoo-user@lists.gentoo.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