From: Michael Unterkalmsteiner <miciu@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc compilation problem
Date: Mon, 9 Mar 2009 20:09:25 +0100 [thread overview]
Message-ID: <200903092009.25554.miciu@gmx.de> (raw)
Hi,
I'd like to build a toolchain for mips with nommu (using buildroot-2009.02). I
get the following error:
[...]
CC libc/stdio/tmpnam.o
CC libc/stdio/tmpnam_r.o
CC libc/stdio/popen.o
libc/stdio/popen.c:45: error: 'fork' undeclared here (not in a function)
libc/stdio/popen.c:45: warning: type defaults to 'int' in declaration of
'fork'
libc/stdio/popen.c: In function 'popen':
libc/stdio/popen.c:100: error: called object 'fork' is not a function
[...]
The problematic part in popen.c is:
[...]
/* uClinux-2.0 has vfork, but Linux 2.0 doesn't */
#include <sys/syscall.h>
#if ! defined __NR_vfork
# define vfork fork
# define VFORK_LOCK ((void) 0)
# define VFORK_UNLOCK ((void) 0)
libc_hidden_proto(fork)
#endif
[...]
I'm wondering why __NR_vfork is not defined...
Can someone give me a punch into the right direction?
Thanks,
Michael
next reply other threads:[~2009-03-09 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 19:09 Michael Unterkalmsteiner [this message]
2009-03-09 20:06 ` [Buildroot] uClibc compilation problem Peter Korsgaard
2009-03-09 22:17 ` Michael Unterkalmsteiner
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=200903092009.25554.miciu@gmx.de \
--to=miciu@gmx.de \
--cc=buildroot@busybox.net \
/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