Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: renxuefeng <renxf_maillist@126.com>
To: buildroot@busybox.net
Subject: [Buildroot] How can i compile bash3.1 with uclibc
Date: Tue, 10 Oct 2006 22:02:15 +0800	[thread overview]
Message-ID: <452BA7E7.9060704@126.com> (raw)
In-Reply-To: <901e5e350610100506t1574b963u5dcf77b34a9967ad@mail.gmail.com>

Thanks Michael.
I have done using  your method. Now I can compile the bash sucessfully.
but i don't know whether there will be some problem. I know fork and 
vfork have some differences.
> You should add the following option to gcc
>
> CFLAGS += -Dfork=vfork
>
> On 10/10/06, *renxuefeng* <renxf_maillist@126.com 
> <mailto:renxf_maillist@126.com>> wrote:
>
>     i met a problem When i build buildroot with uclibc.
>     while compiling the bash3.1, it showed some error:
>
>     nojobs.o: In function `make_child':
>     nojobs.c:(.text+0x464): undefined reference to `fork'
>
>     I thought this is because the uclibc didnot support the fork function
>     under the armnommu platform
>     but how can i using bash under uclibc.
>     does anybody have some patch for this problem.
>
>
>
>
>     _______________________________________________
>     buildroot mailing list
>     buildroot at uclibc.org <mailto:buildroot@uclibc.org>
>     http://busybox.net/mailman/listinfo/buildroot
>
>

  parent reply	other threads:[~2006-10-10 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 10:55 [Buildroot] How can i compile bash3.1 with uclibc renxuefeng
     [not found] ` <901e5e350610100506t1574b963u5dcf77b34a9967ad@mail.gmail.com>
2006-10-10 14:02   ` renxuefeng [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-10 12:53 Michael

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=452BA7E7.9060704@126.com \
    --to=renxf_maillist@126.com \
    --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