From: Ulrich Drepper <drepper@cygnus.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: changes to stdlib/longlong.h
Date: Tue, 23 Nov 1999 07:14:00 -0000 [thread overview]
Message-ID: <m3d7t1mecz.fsf@localhost.localnet> (raw)
In-Reply-To: <19991123120104.I515@mff.cuni.cz>
Jakub Jelinek <jakub@redhat.com> writes:
> What was the reason to update longlong.h from egcs which seem to have a
> subset of the glibc longlong stuff?
This is the master version and whenever a change is only in the glibc
version something is wrong. I had problems with the original file on
one platform and the update fixed it.
So, which are the definitions you are missing? I can of course add
them back but you'll also have to send them to the gcc people to be
included.
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
next prev parent reply other threads:[~1999-11-23 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-23 2:59 Jakub Jelinek
1999-11-23 7:14 ` Ulrich Drepper [this message]
1999-11-23 9:20 ` Jakub Jelinek
1999-11-23 9:26 ` Ulrich Drepper
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=m3d7t1mecz.fsf@localhost.localnet \
--to=drepper@cygnus.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sourceware.cygnus.com \
/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).