From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: 1.1.4 incompatible with glibc 2.1
Date: Sat, 04 Jan 2003 18:38:42 +0300 [thread overview]
Message-ID: <3E170002.3050800@yahoo.com> (raw)
Hello.
Sergey Suleymanov wrote:
> Glibc-2.2 has
> typedef uint32_t in_addr_t;
> in /usr/include/netinet/in.h. Glibc-2.1 hasn't. :(
Yes, I understand that this error means
a missing definition. What am I trying to
say is that it looks like a bug of a
particular glibc version, so that no
modifications to dosemu required at all,
just "upgrade your glibc" message.
We can always hardcode that size to 4,
but what if midid will use IPv6 one day? :)
Could you, btw, please search for that
definition in the other headers? I can't
beleive it can be simply missing, after
reading "man inet".
It would be the best to add an in_addr_t
check to configure and define it ourselves
if it is missing, but probably this is just
too much for such a small thing:)
next reply other threads:[~2003-01-04 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-04 15:38 Stas Sergeev [this message]
2003-01-05 6:10 ` 1.1.4 incompatible with glibc 2.1 Sergey Suleymanov
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 10:17 Stas Sergeev
2003-01-04 10:58 Stas Sergeev
2003-01-04 11:10 ` Sergey Suleymanov
2003-01-04 10:05 Sergey Suleymanov
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=3E170002.3050800@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@vger.kernel.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