Problem reapplying patch for the HIXS system

[Jeff Johnston]

On 12/07/2010 02:39 PM, Michael Ambrus wrote:
> Hi,
> A few years back I experimented with a system which I called HIXS in
> newlib-1.14.0/newlib/libc/sys/. I'm trying to re-apply the patch (which
> used to work perfectly) to newlib-1.18.0 but for some reason it won't
> build.
>
> Adding an extra printout in HIXS configure.in:
>
> AC_MSG_NOTICE([===== Running configure for HIXS<$PACKAGE_NAME>  version
> <$PACKAGE_VERSION>  ====])
>
> As far as I can see from from the build/configure logs, the configure
> script for hixs is never run. A snippet from the build however shows:
>
> ==========================================================================================
> Making all in sys
> make[8]: Entering directory
> `/tmp/BO/arm-hixs-elf/newlib-1.18.0/arm-hixs-elf/thumb/newlib/libc/sys'
> Making all in hixs
> /bin/bash: line 17: cd: hixs: No such file or directory
> Making all in .
> make[9]: Entering directory
> `/tmp/BO/arm-hixs-elf/newlib-1.18.0/arm-hixs-elf/thumb/newlib/libc/sys'
> make[9]: *** No rule to make target `hixs/lib.a', needed by `lib.a'.
> ==========================================================================================
>
> Seems the build-system has got it half-way right. It expects HIXS to be
> where it should, but it has not created the directory nor run the the
> configure script for it?
>
> What's happened, has there been there any fundamental changes in the
> build-system or am I missing something (forgotten but) obvious?
>
> Any input/hints much appreciated.
>
> Regards
> Michael Ambrus
> http://kato.homelinux.org/~tinker/
>
>

Look at newlib/libc/sys/configure.in.  You have to tell it to configure 
your hixs subdir via the sys_dir variable which you set in newlib's 
top-level file: configure.host.  Remember to run autoconf after you 
change configure.in.