From: Juanma Barranquero <lekktu@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 9010@debbugs.gnu.org
Subject: bug#9010: sigprocmask -> pthread_sigmask for Emacs
Date: Sat, 9 Jul 2011 01:29:28 +0200 [thread overview]
Message-ID: <CAAeL0SR2CzReVCrCOqHmgU8rRbZnN6LiJ9Ut6e0v39RXeGagNQ@mail.gmail.com> (raw)
In-Reply-To: <4E176BC9.1000306@cs.ucla.edu>
On Fri, Jul 8, 2011 at 22:42, Paul Eggert <eggert@cs.ucla.edu> wrote:
> OK, I installed the patch into the trunk as bzr 105047.
> This is a bit different from the earlier patch, as both
> Emacs and gnulib have mutated in the meantime, but I don't
> think the differences affect w32 or msdos.
Oh, I'd say it does indeed:
oo-spd/i386/temacs1.a(process.o): In function `create_process':
C:\emacs\trunk\src/process.c:1655: undefined reference to `pthread_sigmask'
C:\emacs\trunk\src/process.c:1811: undefined reference to `pthread_sigmask'
C:\emacs\trunk\src/process.c:1903: undefined reference to `pthread_sigmask'
C:\emacs\trunk\src/process.c:1903: undefined reference to `pthread_sigmask'
oo-spd/i386/temacs2.a(sysdep.o): In function `sys_sigblock':
C:\emacs\repo\trunk\src/sysdep.c:1537: undefined reference to `pthread_sigmask'
oo-spd/i386/temacs2.a(sysdep.o):C:\emacs\trunk\src/sysdep.c:1545: more
undefined references to `pthread_sigmask' follow
collect2: ld returned 1 exit status
make[1]: *** [oo-spd/i386/temacs.exe] Error 1
make[1]: Leaving directory `C:/emacs/trunk/src'
make: *** [all-other-dirs-gmake] Error 2
Juanma
next prev parent reply other threads:[~2011-07-08 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 18:11 bug#9010: sigprocmask -> pthread_sigmask for Emacs Paul Eggert
2011-07-07 8:01 ` Jan Djärv
2011-07-08 7:17 ` Eli Zaretskii
2011-07-08 9:58 ` Paul Eggert
2011-07-08 10:16 ` Eli Zaretskii
2011-07-08 20:42 ` Paul Eggert
2011-07-08 23:29 ` Juanma Barranquero [this message]
2011-07-08 23:32 ` Paul Eggert
2011-07-09 0:13 ` Juanma Barranquero
2011-07-09 7:02 ` 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=CAAeL0SR2CzReVCrCOqHmgU8rRbZnN6LiJ9Ut6e0v39RXeGagNQ@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=9010@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.