building "ipkg" for a PPC -- progress report

  observations about my ongoing quest to build ipkg for a PPC-based
evaluation board. just to summarize what i've seen so far:

1) apparent typo in latest CVS version of autoconfigure.sh --
   $(HOST) -> ${HOST}

2) curious warnings from autoconfigure.sh:

+ aclocal
+ autoconf
+ autoheader
+ automake -a -c
Makefile.am:5: `CFLAGS' is a user variable, you should not override it;
Makefile.am:5: use `AM_CFLAGS' instead.
libbb/Makefile.am:3: `CFLAGS' is a user variable, you should not override
it;
libbb/Makefile.am:3: use `AM_CFLAGS' instead.
+ ./configure --host=ppc-linux
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.

3) i notice that the generated Makefile does not have a variable setting
   for

   LD=ppc-linux-ld

   should it? to be fair, i didn't need to set it for my build, but i
   just thought it might be consistent (although i'm a real newbie when
   it comes to autoconf and automake)

all of the above taken into account, the "make" ran to completion, and
i have an ipkg executable:

$ file ipkg
ipkg: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV),
for GNU/Linux 2.2.5, dynamically linked (uses shared libs), not stripped

  i can't test it at the moment, but the fact that it exists and has the
right properties gives me hope.

  any further advice i should get before trying to install and test it on
the eval board later today? (perhaps i should have first tried to build
it statically just to avoid any lib problems on the first test. is this
generally considered a good thing to do for a first attempt?)

  thanks for everyone's help.

rday

i guess it's time to build an entire toolchain for my zaurus 5500.
yee ha.
Received on Mon Nov 17 09:22:15 2003