all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 18237@debbugs.gnu.org
Subject: bug#18237: Small fix for MSDOS
Date: Sun, 10 Aug 2014 21:26:47 +0300	[thread overview]
Message-ID: <83iom0jj4o.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdoh9=1OTnjQO9x-mZWZpU_v8eNMJqFHke83GT5P2zj5eNQ@mail.gmail.com>

> Date: Sun, 10 Aug 2014 19:19:24 +0100
> From: Reuben Thomas <rrt@sc3d.org>
> Cc: 18237@debbugs.gnu.org
> 
> When it is installed, configure correctly detects that select is available,
> and sets HAVE_SELECT. However, libsocket has no sys/select.h, nor does it
> implement sys_select.
> 
> Hence, at present, when I build using ./configure && make for DOS with
> libsocket installed, HAVE_SELECT is defined to 1, so the MS-DOS
> implementation of sys_select in msdos.c is not compiled. Later, the linker
> is unable to find sys_select, and the build fails.

So it's a consequence of trying to configure using the Posix configure
script.

I'd prefer that all the changes for such a build be committed at once
together, not bit by bit, and only if you eventually succeed to
produce a working binary using this method.

> I think you're also saying that I should test both HAVE_SELECT &&
> HAVE_SYS_SELECT_H therefore?

Yes, at the very least.  But let's delay this until you have gone all
the way to building Emacs using this method.  We won't know all of the
implications until you do.





  reply	other threads:[~2014-08-10 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10 16:40 bug#18237: Small fix for MSDOS Reuben Thomas
2014-08-10 18:02 ` Eli Zaretskii
2014-08-10 18:19   ` Reuben Thomas
2014-08-10 18:26     ` Eli Zaretskii [this message]
2014-08-10 18:42       ` Reuben Thomas
2014-08-10 19:05         ` Eli Zaretskii

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=83iom0jj4o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18237@debbugs.gnu.org \
    --cc=rrt@sc3d.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.