All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: 1.1.4 incompatible with glibc 2.1
Date: Sun, 05 Jan 2003 13:17:38 +0300	[thread overview]
Message-ID: <3E180642.1030803@yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 507 bytes --]

Hello.

Sergey Suleymanov wrote:
> Stas> dosemu required at all, just "upgrade your glibc" message.  
> Wow! :) That's sort of using a steam-hammer to crack nuts.
Yes:)

> 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
That makes sense.
OK, as the in_addr_t is not really used
(only once for sizeof), then there should
be no problems at all avoiding it entirely.
The attached trivial patch should do the trick.

[-- Attachment #2: timid.diff --]
[-- Type: text/plain, Size: 498 bytes --]

--- src/arch/linux/dosext/sound/midid/timid.c	Sat Jan  4 15:40:30 2003
+++ src/arch/linux/dosext/sound/midid/timid.c	Sun Jan  5 13:04:50 2003
@@ -102,7 +102,7 @@
   
   ctrl_adr.sin_family = AF_INET;
   ctrl_adr.sin_port = htons(config.timid_port);
-  memcpy(&ctrl_adr.sin_addr.s_addr, serv->h_addr, sizeof(in_addr_t));
+  memcpy(&ctrl_adr.sin_addr.s_addr, serv->h_addr, sizeof(ctrl_adr.sin_addr.s_addr));
 
   data_adr.sin_family = AF_INET;
   data_adr.sin_addr.s_addr = ctrl_adr.sin_addr.s_addr;

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05 10:17 Stas Sergeev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-04 15:38 1.1.4 incompatible with glibc 2.1 Stas Sergeev
2003-01-05  6:10 ` Sergey Suleymanov
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=3E180642.1030803@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.