trying to build latest CVS ipkg for powerpc

  after a couple of attempts, i'm still trying to build a version of ipkg
for a powerpc-based board (RPX850L running a 2.4.7-based linux from
timesys), and i have a couple questions about the build specifically, and
about the general build procedure for stuff i check out of
cvs.handhelds.org. (a pointer to an online doc would do fine.)

  first, i didn't see a PPC-based toolchain available at handhelds.org.
(and by PPC, i mean powerpc.) not that it's a big deal, i already have
the timesys toolchain, and i just downloaded another from intrinsyc.com,
but is there a recommended PPC toolchain? as it is, i have all the
necessary utilities in /usr/local/ppc860-linux/bin, which is part of
my search path, but i'm wondering what others are using (although i can
see that handhelds.org is heavily ARM-influenced).

  first issue -- i checked out "ipkg" from CVS, and noticed right away,
there was no "configure" script, so i'm assuming i have to run the
autotools manually. what's the correct incantation? the results of
what i would normally expect to run:

$ aclocal
$ autoheader
$ automake --add-missing
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.
$ autoconf

is this the correct recipe to apply to any stuff i check out of
handhelds CVS? (should i care about the diagnostics from automake?)

  next, do the configure with:

$ ./configure --host=powerpc-linux # right?
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.
... etc etc ...

  huh? was this not the right incantation? i'm doing this build on an
x86 box running red hat FC 1. am i not supposed to specify a host of
powerpc-linux? am i misunderstanding something fundamental here?
regardless, the configure finishes, and when i check the generated
Makefile, i notice the common cross-compile variables i expect to see:

  CC = powerpc-linux-gcc
  CPP = powerpc-linux-gcc -E
  STRIP = powerpc-linux-strip

and so on. but not for LD. shouldn't i expect to also see

  LD = powerpc-linux-ld

which exists in the toolchain bin/ directory. why shouldn't this be
there?

  so finally, i just run "make", which terminates with:

ipkg_conf.o: In function `ipkg_conf_init':
/home/rpjday/t/ipkg/ipkg_conf.c:122: undefined reference to `mkdtemp'
/home/rpjday/t/ipkg/ipkg_conf.c:122: relocation truncated to fit:
R_PPC_REL24 mkdtemp
ipkg_install.o: In function `unpack_pkg_control_files':
/home/rpjday/t/ipkg/ipkg_install.c:488: undefined reference to `mkdtemp'
/home/rpjday/t/ipkg/ipkg_install.c:488: relocation truncated to fit:
R_PPC_REL24 mkdtemp
collect2: ld returned 1 exit status
make[2]: *** [ipkg] Error 1
make[2]: Leaving directory `/home/rpjday/t/ipkg'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/rpjday/t/ipkg'
make: *** [all] Error 2
[rpjday_at_localhost ipkg]$

  re-running this as:

$ make LD=powerpc-linux-ld

didn't make any difference. so, some general questions:

1) is there a recommended PPC toolchain i should use?
2) what is the recommended recipe for checking out and building
   packages from cvs.handhelds.org?
3) any advice on the above error?

thanks muchly for any help.

rday
Received on Fri Nov 14 2003 - 11:57:03 EST