From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [LUATEX] uname() volunteers needed
Date: Wed, 21 May 2008 14:11:14 +0200 [thread overview]
Message-ID: <48341162.2000008@elvenkind.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
Hi all,
This is a little offtopic (it deals with luatex only) but as
Mojca said: there are many more luatex-using people here than
on dev-luatex.
In a discussion with Yue Wang he convinced me that it would
be better to use uname() for finding os.name instead of the
current jungle of #ifdefs.
Because I do not want to alter the lua return values, that
means I will have to interpret the contents of the returned
structure a bit. To do that, I would appreciate it if the people
on a non-linux32intel platform would compile and run the
attached minimalistic C file.
Thanks in advance,
Taco
[-- Attachment #2: test-uname.c --]
[-- Type: text/x-csrc, Size: 380 bytes --]
#include <sys/utsname.h>
#include <stdio.h>
int main () {
struct utsname uts;
if (uname(&uts)) {
puts("uname() failed");
} else {
printf("sysname: %s\n", uts.sysname);
printf("nodename: %s\n", uts.nodename);
printf("release: %s\n", uts.release);
printf("version: %s\n", uts.version);
printf("machine: %s\n", uts.machine);
}
return 0;
}
[-- Attachment #3: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2008-05-21 12:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 12:11 Taco Hoekwater [this message]
2008-05-21 12:25 ` Thomas A. Schmitz
2008-05-21 12:59 ` Yue Wang
2008-05-21 13:44 ` Thomas A. Schmitz
2008-05-21 12:43 ` Jin-Hwan Cho
2008-05-21 13:43 ` Arthur Reutenauer
2008-05-21 14:26 ` Yue Wang
2008-05-21 20:22 ` Martin Schröder
2008-05-21 22:00 ` Arthur Reutenauer
2008-05-21 22:15 ` Martin Schröder
2008-05-21 23:59 ` Arthur Reutenauer
2008-05-22 10:26 ` Yue Wang
2008-05-22 11:21 ` Taco Hoekwater
2008-05-22 13:50 ` luigi scarso
2008-05-22 14:11 ` Hans Hagen
2008-05-22 14:18 ` luigi scarso
2008-05-22 11:28 ` Hans Hagen
2008-05-21 18:40 ` Peter Münster
2008-05-21 19:42 ` Diego Depaoli
2008-05-21 20:09 ` Gour
2008-05-21 20:35 ` Michael Hallgren
2008-05-22 12:22 ` Taco Hoekwater
2008-05-22 23:39 ` [LUATEX] " Mojca Miklavec
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=48341162.2000008@elvenkind.com \
--to=taco@elvenkind.com \
--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).