ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans van der Meer <hansm@science.uva.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: luatex not compiling
Date: Mon, 24 Dec 2007 13:12:07 +0100	[thread overview]
Message-ID: <4095B4DD-6293-4B54-A526-830330345F87@science.uva.nl> (raw)
In-Reply-To: <68c491a60712210250y29b0ef31y4e01fe54e848ba41@mail.gmail.com>

I looked somewhat further and found out the curious fact that on  
MacOSX 10.5.x both /usr/include/signal.h and /usr/include/sys/signal.h  
exist!
The first one does not include the second one, neither does one of the  
includes:
#ifndef _USER_SIGNAL_H
#define _USER_SIGNAL_H
#include <sys/cdefs.h>
#include <_types.h>

As for changing the discussion to the luatex developer list as  
suggested by some: my capacity for subscribing list is limited --  
capacity in the sense of what I can manage.
Putting my observations on the compiler problem with luatex on this  
list was purely to help others. I hope one will permit me to keep  
doing so.

Hans van der Meer



On 21 dec 2007, at 11:50, Martin Schröder wrote:

> 2007/12/20, Hans van der Meer <hansm@science.uva.nl>:
>> Probably changing the code into:
>> #include <signal.h>
>> #ifndef _SIGNAL_H_
>> #include <sys/signal.h>
>> #endif
>> might help, but I have not tested this (some of the pie should be  
>> left
>> for Taco c.s. ;-)
>
> Just curious: What does the man page of signal.h say how to include
> it on OSX? On linux it's <signal.h> ...
>
> Best
>   Martin
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an  
> entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2007-12-24 12:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 18:05 Hans van der Meer
2007-12-21 10:50 ` Martin Schröder
2007-12-21 15:10   ` Idris Samawi Hamid
2007-12-21 15:27     ` Taco Hoekwater
2007-12-23 20:25       ` [Dev-luatex] " Jjgod Jiang
2007-12-24 20:50         ` Taco Hoekwater
2007-12-25  3:14           ` Jjgod Jiang
2007-12-25  7:43             ` Taco Hoekwater
2007-12-25 10:13           ` Yannis Haralambous
2007-12-26  9:13             ` luigi scarso
2007-12-26 11:54             ` Otared Kavian
2007-12-21 17:49     ` luigi scarso
2007-12-24 12:12   ` Hans van der Meer [this message]
2007-12-24 20:45     ` Taco Hoekwater

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=4095B4DD-6293-4B54-A526-830330345F87@science.uva.nl \
    --to=hansm@science.uva.nl \
    --cc=ntg-context@ntg.nl \
    /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;
as well as URLs for NNTP newsgroup(s).