public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Suleymanov <solt@eatpbank.ru>
To: Linux-MSDOS Mailing list <linux-msdos@vger.kernel.org>
Subject: Re: 1.1.4 incompatible with glibc 2.1
Date: 05 Jan 2003 09:10:09 +0300	[thread overview]
Message-ID: <87vg14ktz2.fsf@boo.eatpbank.ru> (raw)
In-Reply-To: <3E170002.3050800@yahoo.com>

>>>>> Stas Sergeev writes:

 Stas> Yes, I understand that this error means a missing
 Stas> definition. What am I trying to say is that it looks like a bug
 Stas> of a particular glibc version, so that no modifications to
 Stas> dosemu required at all, just "upgrade your glibc" message.  

        Wow! :) That's sort of using a steam-hammer to crack nuts.

 Stas> We can always hardcode that size to 4, but what if midid will
 Stas> use IPv6 one day? :) Could you, btw, please search for that
 Stas> definition in the other headers?

        Nothing.

 Stas> I can't beleive it can be simply missing, after reading "man
 Stas> inet".  

        I read it too. And saw just unsigned long int :) System is
        Debian 2.2 (Potato)

 Stas> It would be the best to add an in_addr_t check to configure and
 Stas> define it ourselves if it is missing, but probably this is just
 Stas> too much for such a small thing:)

        :) Well, 1.1.4 is a development release. I think when 1.2 is
        out glibc will be 5.x ;)

-- 
  Sergey Suleymanov


  reply	other threads:[~2003-01-05  6:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04 15:38 1.1.4 incompatible with glibc 2.1 Stas Sergeev
2003-01-05  6:10 ` Sergey Suleymanov [this message]
  -- 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=87vg14ktz2.fsf@boo.eatpbank.ru \
    --to=solt@eatpbank.ru \
    --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