error in building the tools on debian etch

[scharkalvin]

I am following the directions to build the tools in
http://www.rockbox.org/twiki/bin/view/Main/CrossCompiler
for the "automatic build".  I downloaded the latest souces and
as root executed the rockboxdev.sh script.  
I am running amd64 debian etch.

I am getting the following output to running the script:

== Summary ==
Target: arm-elf
gcc 4.0.3
gcc patch thumb-interwork-4.0.3.diff
binutils 2.16.1
install in /usr/local/arm-elf
when complete, make your PATH include /usr/local/arm-elf/bin
binutils 2.16.1 already downloaded
gcc 4.0.3 already downloaded
thumb-interwork-4.0.3.diff already downloaded
ROCKBOXDEV: extracting binutils-2.16.1 in /tmp/rbdev-build
ROCKBOXDEV: extracting gcc-4.0.3 in /tmp/rbdev-build
ROCKBOXDEV: applying gcc patch
patching file ./gcc-4.0.3/gcc/config/arm/t-arm-elf
ROCKBOXDEV: mkdir build-binu
ROCKBOXDEV: cd build-binu
ROCKBOXDEV: binutils/configure
creating cache ./config.cache
checking host system type... x86_64-unknown-linux-gnu
checking target system type... arm-unknown-elf
checking build system type... x86_64-unknown-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.
ROCKBOXDEV: binutils/make
make: *** No targets specified and no makefile found.  Stop.
ROCKBOXDEV: binutils/make install to /usr/local/arm-elf
make: *** No rule to make target `install'.  Stop.
ROCKBOXDEV: mkdir build-gcc
ROCKBOXDEV: cd build-gcc
ROCKBOXDEV: gcc/configure
creating cache ./config.cache
checking host system type... x86_64-unknown-linux-gnu
checking target system type... arm-unknown-elf
checking build system type... x86_64-unknown-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.
ROCKBOXDEV: gcc/make
make: *** No targets specified and no makefile found.  Stop.
ROCKBOXDEV: gcc/make install to /usr/local/arm-elf
make: *** No rule to make target `install'.  Stop.
done

Make your PATH include :/usr/local/arm-elf/bin

the "set" command shows the PATH variable as:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11

also
ls /usr/local
yeilds:
bin  etc  games  include  jre1.6.0_01  jre-6u1-linux-amd64.bin  lib  man  sbin  share  src

[krazykit]

It sounds like you don't have your toolchain set up in Debian.  Try running "aptitude install build-essential" as root, then re-running rockboxdev.sh

[scharkalvin]

It sounds like you don't have your toolchain set up in Debian.  Try running "aptitude install build-essential" as root, then re-running rockboxdev.sh

Debian must have changed in recent years.  In the past GCC et-al was always installed by default.  Ubuntu requires that you install the tools.  Anyway I did apt-get install gcc.
I'll try the build essential target and see what happens.

[scharkalvin]

Thanks, that seems to have done it.
Egad's, Debian has become Ubuntuized!  This is the first
time I had to install code generation tools in Debian.
Wasn't like that up till and including Woody.
(I just switched from Gentoo to Etch, and it's a bit of a shock.
I really liked Gentoo, but it finally got terminally broken due to
the developers not knowing when to keep their fingers out of
the plumbing....)

[GodEater]

I really liked Gentoo, but it finally got terminally broken due to
the developers not knowing when to keep their fingers out of
the plumbing....)

OT:

Odd - my gentoo install is still working fine...

[scharkalvin]

Odd - my gentoo install is still working fine...

If you keep up to date with all the latest ebuilds (so you don't have
to emerge too much at the same time) the system is usually stable.
I ran into trouble not touching the system for 6 months and then
doing an emerge to update everything.  Portage simply got lost and
confused.  Gentoo isn't the same since Daniel left. (sigh!).

 

[GodEater]

Really really OT:

crontab is your friend

[scharkalvin]

I downloaded the sources from svn and tried to compile.
I did a configure for the sansa e200 (50) and a normal build.

The make command seems to have worked.

make zip fails:
ken@Janus:~/rockboxdev/rockbox/build$ make zip
xargs: zip: No such file or directory

Here's whats in my build directory after make runs...
ken@Janus:~/rockboxdev/rockbox/build$ ls
apps         lang.c            libbitmapsnative.a  libm4a.a             libpluginbitmapsmono.a    libTremor.a    rockbox-info.txt
autoconf.h   lang.h            libcodec.a          libmad.a             libpluginbitmapsnative.a  libwavpack.a   rockbox.mi4
bitmaps      liba52.a          libdemac.a          libmad-mpegplayer.a  librockbox.a              libwma.a       sysfont.h
credits.raw  libalac.a         libfaad.a           libmusepack.a        libspc.a                  Makefile
firmware     libbitmapsmono.a  libffmpegFLAC.a     libplugin.a          libspeex.a                pluginbitmaps

ken@Janus:~/rockboxdev/rockbox/build$ ls apps
abrepeat.o    codecs        dsp.o         filetypes.o  main.o      onplay.o            plugin.o     root_menu.o      status.o
action.o      codecs.o      enc_config.o  gui          menu.o      pcmbuf.o            plugins      screen_access.o  tagcache.o
alarm_menu.o  cuesheet.o    eq_arm.o      keymaps      menus       playback.o          recorder     screens.o        tagtree.o
audio_path.o  debug_menu.o  eq.o          lang.o       metadata    playlist_catalog.o  rockbox.bin  scrobbler.o      talk.o
bitmaps       dep-apps      features      language.o   metadata.o  playlist.o          rockbox.elf  settings_list.o  tree.o
bookmark.o    dsp_arm.o     filetree.o    linkage.lds  misc.o      playlist_viewer.o   rockbox.map  settings.o

ken@Janus:~/rockboxdev/rockbox/build$ ls firmware
arabjoin.o         buffer.o      drivers       general.o  kernel.o   pcm.o         replaygain.o     sysfont.c  thread.o
ata_idle_notify.o  common        enc_base.o    hangul.o   lru.o      pcm_record.o  rolo.o           sysfont.o  timer.o
backlight.o        debug.o       font_cache.o  hotswap.o  mp3data.o  pcm_sampr.o   scroll_engine.o  system.o   tuner.o
bidi.o             dep-firmware  font.o        id3.o      panic.o    powermgmt.o   sound.o          target     usb.o

[cool_walking_]

Umm... got zip installed?

[GodEater]

apparently not

[scharkalvin]

I do have unzip installed, which I thought was the same package as zip but with a different launch option.  Also have gzip installed.  I'll have to check and see which debian packages actually provide which commands.

Another question:  Do I need to build a rockbox image for a player before I can build a
simulator for the same player?  When I tried to build the simulator it seemed to build, but the build install failed in that it did NOT create or populate the .rockbox directory for the simulator.

[GodEater]

Another question:  Do I need to build a rockbox image for a player before I can build a
simulator for the same player?  When I tried to build the simulator it seemed to build, but the build install failed in that it did NOT create or populate the .rockbox directory for the simulator.

No you don't need anything to do with the rockbox image for the player built in order to build a simulator for it.

What did "make install" say when it failed ?

[scharkalvin]

Something about not finding zip files ... I'll try it again tonight after installing the debian zip package.  Funny, the make call did NOT seem to fail because I didn't have zip installed, only did that when building the target image, and then only in the step make zip.   Did I need to build fonts first?

[scharkalvin]

I installed the debian zip package and now everything works.  I don't quite understand why the zip utility is needed to build and install the simulator, it shouldn't be necessary to zip and unzip files, just copy them into the target directory.
Anyway the make install for the simulator now works.

[bluebrother]

I don't quite understand why the zip utility is needed to build and install the simulator, it shouldn't be necessary to zip and unzip files, just copy them into the target directory.
Anyway the make install for the simulator now works.

Because installation works the same way as creating a build: the required files get zipped up and unzipped to the target (which is a folder for the sim). This makes the process easier. And you ran "make zip" in the first post, which (unsurprisingly due to the target name "zip") implies that you need zip.

Feel free to submit a patch to remove the dependency on zip for simulator installation.