gnu.bash.bug
[Top] [All Lists]

Re: problems cross-compling bash-3.2

Subject: Re: problems cross-compling bash-3.2
From: Mike Frysinger
Date: Tue, 28 Aug 2007 10:05:44 -0400
Newsgroups: gnu.bash.bug
On Tuesday 28 August 2007, Christian Boon wrote:
> Christian Boon wrote:
> > Chet Ramey wrote:
> >> Christian Boon wrote:
> >>> Hello,
> >>>
> >>> i want to cross compile bash-3.2 for my pxa255 arm processor and its
> >>> working although i can't get job control working.
> >>
> >> It tells you it won't be able to:
> >>> checking for presence of necessary job control definitions...
> >>> configure:
> >>> WARNING: cannot check job control if cross-compiling -- defaulting to
> >>> missing
> >>> missing
> >>
> >> You can look at the definition of BASH_SYS_JOB_CONTROL_MISSING in
> >> aclocal.m4 and manually check which, if any, of the conditions is
> >> not met.
> >>
> >> Chet
> >
> > This is from aclocal.m4:
> >
> > AC_DEFUN(BASH_SYS_JOB_CONTROL_MISSING,
> > [AC_REQUIRE([BASH_SYS_SIGNAL_VINTAGE])
> > AC_MSG_CHECKING(for presence of necessary job control definitions)
> > AC_CACHE_VAL(bash_cv_job_control_missing,
> > [AC_TRY_RUN([
> > #include <sys/types.h>
> > #ifdef HAVE_SYS_WAIT_H
> > #include <sys/wait.h>
> > #endif
> > #ifdef HAVE_UNISTD_H
> > #include <unistd.h>
> > #endif
> > #include <signal.h>
>
> Does anybody know what is going wrong or what is missing?

nothing is wrong ... as Chet pointed out, look at the autotools snippet to 
figure out what variable *you* need to set in your environment before 
executing configure in order to force the check to go the way you want
-mike
<Prev in Thread] Current Thread [Next in Thread>