Author Topic: Can't compile the with the Toolchain.  (Read 7271 times)

LuckyLights (OP)

  • *
  • Posts: 6
Can't compile the with the Toolchain.
« on: October 28, 2013, 03:50:20 pm »
Hi,

I'm a Android and iOS game engine developer from Sweden, and I'm really excited to get started working on my GWC Zero project now that there is OpenGLES support. I have no previous knowledge of linux development (Android dos not count).

I have spent the last couple hours trying to get the Toolchain setup on a Ubunto 12.04 dist. I have been trying to compile the Liero (https://github.com/gcwnow/liero) code sense this is the only "Sample'ish Project" I can find for the Toolchain.

I have tried to compile using both the "2013-10-04" and the "2013-09-13" version of the Toolchain both from the /opt/ folder and my home folder. Both calling make from sudo and not.

Every setup i have tried so far have ended up with:
Code: [Select]
/opt/gcw0-toolchain/usr/bin/mipsel-linux-g++ -mips32 -mtune=mips32 -G0 -fomit-frame-pointer -ffunction-sections -ffast-math -fsingle-precision-constant -mbranch-likely -c -O2 -I/opt/gcw0-toolchain/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/include/ -I/opt/gcw0-toolchain/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/include/SDL blit.cpp -o blit.o
make: /opt/gcw0-toolchain/usr/bin/mipsel-linux-g++: Command not found
make: *** [blit.o] Error 127

In fact all of the compiler links seams to not be nonvalid (mipsel-linux-gpp, mipsel-linux-c++, etc.).

I just really want to get started Is there any other sample project that would be a better starting point?

hi-ban

  • **
  • Posts: 863
Re: Can't compile the with the Toolchain.
« Reply #1 on: October 28, 2013, 03:56:17 pm »
Did you check that the paths in the makefile match with the paths of the toolchain in your computer?
If they don't match, you should modify the makefile.

LuckyLights (OP)

  • *
  • Posts: 6
Re: Can't compile the with the Toolchain.
« Reply #2 on: October 28, 2013, 04:18:10 pm »
Yes I have most definitely, multiple times, every time i changed the location of cgw0-toolchain. I also tried to call the compilers my self, it wont be found unless i call it as sudo. It cant produce any .o files even when it is found ???

dmitry_smagin

  • *
  • Posts: 421
Re: Can't compile the with the Toolchain.
« Reply #3 on: October 28, 2013, 04:38:11 pm »
Enter this in the shell:

export PATH=$PATH:/opt/gcw0-toolchain/usr/bin/

And then mipsel-linux-gcc becomes available.
GCW-Zero prototype, Dingoo a320, Ritmix rzx-50, Dingoo a380, Xperia Play

LuckyLights (OP)

  • *
  • Posts: 6
Re: Can't compile the with the Toolchain.
« Reply #4 on: October 28, 2013, 05:35:19 pm »
Yhea did that too =(

ends up like this:
Code: [Select]
[email protected]:~$ sudo mipsel-linux-g++
sudo: mipsel-linux-g++: command not found
« Last Edit: October 28, 2013, 05:43:14 pm by LuckyLights »

pcercuei

  • ***
  • Posts: 1428
    • My devblog
Re: Can't compile the with the Toolchain.
« Reply #5 on: October 28, 2013, 05:45:09 pm »
Yes I have most definitely, multiple times, every time i changed the location of cgw0-toolchain.
It's "gcw0-toolchain", maybe that's your problem  ;D

LuckyLights (OP)

  • *
  • Posts: 6
Re: Can't compile the with the Toolchain.
« Reply #6 on: October 28, 2013, 05:51:34 pm »
Yes I have most definitely, multiple times, every time i changed the location of cgw0-toolchain.
It's "gcw0-toolchain", maybe that's your problem  ;D

Haha my bad :P. But nope just got it wrong in the post. I really don't get it can it be some form of permission problem?

DiegoSLTS

  • *
  • Posts: 365
Re: Can't compile the with the Toolchain.
« Reply #7 on: October 28, 2013, 05:55:32 pm »
Check if the binaries at /opt/gcw0-toolchain/usr/bin/ are set as executables.

Look at this page to know how to check that: http://www.linux.org/threads/file-permissions-chmod.4094/
Look at this page to set them as executable files if necessary: http://www.thegeekstuff.com/2010/06/chmod-command-examples/

I've had this same problem once when setting up the toolchain for the Dingoo and this solved it.
« Last Edit: October 28, 2013, 05:58:11 pm by DiegoSLTS »

pcercuei

  • ***
  • Posts: 1428
    • My devblog
Re: Can't compile the with the Toolchain.
« Reply #8 on: October 28, 2013, 06:00:55 pm »
It's not a permission problem otherwise you'd get a "permission denied".

Is your Ubuntu 64-bit? If it is, you will need to install additional libraries as the toolchain is 32-bit.

LuckyLights (OP)

  • *
  • Posts: 6
Re: Can't compile the with the Toolchain.
« Reply #9 on: October 28, 2013, 06:11:49 pm »
It's not a permission problem otherwise you'd get a "permission denied".

Is your Ubuntu 64-bit? If it is, you will need to install additional libraries as the toolchain is 32-bit.

Yes! It is 64-bit, what additional libraries do i need?

pcercuei

  • ***
  • Posts: 1428
    • My devblog
Re: Can't compile the with the Toolchain.
« Reply #10 on: October 28, 2013, 06:15:52 pm »
It's not a permission problem otherwise you'd get a "permission denied".

Is your Ubuntu 64-bit? If it is, you will need to install additional libraries as the toolchain is 32-bit.

Yes! It is 64-bit, what additional libraries do i need?
On Debian you have to install the package "ia32-libs", I believe it's the same for Ubuntu.

LuckyLights (OP)

  • *
  • Posts: 6
Re: Can't compile the with the Toolchain.
« Reply #11 on: October 28, 2013, 07:25:21 pm »
It's not a permission problem otherwise you'd get a "permission denied".

Is your Ubuntu 64-bit? If it is, you will need to install additional libraries as the toolchain is 32-bit.

Yes! It is 64-bit, what additional libraries do i need?
On Debian you have to install the package "ia32-libs", I believe it's the same for Ubuntu.

Awesome it worked! Thanks! I have to read up on my linux. And thx for the quick response!

glimmer

  • *
  • Posts: 119
Re: Can't compile the with the Toolchain.
« Reply #12 on: December 09, 2013, 06:46:05 am »
Is your Ubuntu 64-bit? If it is, you will need to install additional libraries as the toolchain is 32-bit.
I'm compiling the toolchain from source right now because I haven't installed a 32-bit Linux distro in years (not counting OpenWRT and OpenDingux), and my development machine has limited disk space, so I really don't want to install a bunch of i386 compat libs. Is there going to be an amd64 build of the toolchain made available in the future, or am I going to have to keep compiling from source?

On the off-chance it might motivate anyone: I'm going to be experimenting with building GZDoom for the Zero... if this toolchain build works.

Thanks!

ETA: The makefile download process is broken in every place it attempts to download files from SF.net. I'm having to download and move the tarballs by hand.
« Last Edit: December 09, 2013, 07:12:12 am by glimmer »

pcercuei

  • ***
  • Posts: 1428
    • My devblog
Re: Can't compile the with the Toolchain.
« Reply #13 on: December 09, 2013, 07:50:45 am »
I believe we could release a 64-bit version of the toolchain next time.

About the download issues on sf.net, last time I tried it worked fine so maybe their FTP is temporarily down?

glimmer

  • *
  • Posts: 119
Re: Can't compile the with the Toolchain.
« Reply #14 on: December 09, 2013, 08:15:07 am »
I believe we could release a 64-bit version of the toolchain next time.

About the download issues on sf.net, last time I tried it worked fine so maybe their FTP is temporarily down?
No, the links that are being passed to wget are coming back as HTML documents, so I'm fairly certain that the URIs are bad.

New update: I can't compile the toolchain for amd64. libtool is an evil, scary thing, so I'm leaving this alone for now:
Code: [Select]
localhost buildroot [2]# make
>>> sdl_mixer 1.2.12 Building
PATH="/usr/src/buildroot/output/host/bin:/usr/src/buildroot/output/host/usr/bin:/usr/src/buildroot/output/host/usr/sbin/:/root/local/scripts:/root/local/apps:/root/local/apps/easyrsa:/usr/lib/colorgcc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" PERLLIB="/usr/src/buildroot/output/host/usr/lib/perl"  /usr/bin/make -j8  -C /usr/src/buildroot/output/build/sdl_mixer-1.2.12/
make[1]: Entering directory `/usr/src/buildroot/output/build/sdl_mixer-1.2.12'
/bin/bash ./libtool --mode=link /usr/src/buildroot/output/host/usr/bin/mipsel-gcw0-linux-uclibc-gcc -o build/libSDL_mixer.la build/effect_position.lo build/effect_stereoreverse.lo build/effects_internal.lo build/load_aiff.lo build/load_voc.lo build/mixer.lo build/music.lo build/music_cmd.lo build/wavestream.lo build/dynamic_mod.lo build/music_mod.lo build/music_modplug.lo build/common.lo build/ctrlmode.lo build/filter.lo build/instrum.lo build/mix.lo build/output.lo build/playmidi.lo build/readmidi.lo build/resample.lo build/sdl_a.lo build/sdl_c.lo build/tables.lo build/timidity.lo build/dynamic_fluidsynth.lo build/fluidsynth.lo build/dynamic_ogg.lo build/load_ogg.lo build/music_ogg.lo    -L/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/lib -lSDL -lpthread -L/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/lib -lmodplug   -lm -no-undefined -rpath /usr/lib -release 1.2 -version-info 12:0:12
libtool: link: warning: library `/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/lib/libSDL.la' was moved.
libtool: link: warning: library `/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/lib/libiconv.la' was moved.
libtool: link: warning: library `/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/lib/libmodplug.la' was moved.
/bin/grep: /usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/lib/gcc/mipsel-gcw0-linux-uclibc/4.8.2/../../../../mipsel-gcw0-linux-uclibc/lib/libstdc++.la: No such file or directory
/bin/sed: can't read /usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/lib/gcc/mipsel-gcw0-linux-uclibc/4.8.2/../../../../mipsel-gcw0-linux-uclibc/lib/libstdc++.la: No such file or directory
libtool: link: `/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/src/buildroot/output/host/usr/lib/gcc/mipsel-gcw0-linux-uclibc/4.8.2/../../../../mipsel-gcw0-linux-uclibc/lib/libstdc++.la' is not a valid libtool archive
make[1]: *** [build/libSDL_mixer.la] Error 1
make[1]: Leaving directory `/usr/src/buildroot/output/build/sdl_mixer-1.2.12'
make: *** [/usr/src/buildroot/output/build/sdl_mixer-1.2.12/.stamp_built] Error 2

glimmer

  • *
  • Posts: 119
Re: Can't compile the with the Toolchain.
« Reply #15 on: December 10, 2013, 10:38:37 pm »
I believe we could release a 64-bit version of the toolchain next time.

About the download issues on sf.net, last time I tried it worked fine so maybe their FTP is temporarily down?
Ubuntu 13.10 no longer has a bulk "ia32-libs" package... probably because they assume that it's been years since they started providing it, so hopefully all those developers out there who were still building for i386 have at least also made amd64 builds available for everyone.

Either updated instructions for distros without an ia32-libs packages, a fixed toolchain source repo that doesn't error out (as detailed above), or (preferably) just an amd64 build of the toolchain would be greatly appreciated.

Until then, I can't start testing GZDoom builds... or anything else.

Sincerely,
Would-be GCW Zero developer...

mth

  • *
  • Posts: 298
Re: Can't compile the with the Toolchain.
« Reply #16 on: December 15, 2013, 08:59:32 pm »
Someone on IRC also had problems with libtool not being able to locate files. It's strange it doesn't build everywhere, since it builds fine for me on both openSUSE and Debian. Can you post the contents of one of the .la files? (they're text files)

Did Ubuntu drop only the bulk package or all 32-bit packages? Since all that the toolchain should need is a 32-bit libc.

I'm not eager to add a 64-bit toolchain to the release, since it would lengthen the time it takes to make a release considerably: the toolchain build takes about 2 hours now and increases as we add packages, plus I'd have to switch VMs halfway the build and upload more files (toolchain is over 100MB; I hope to get fiber in a few months to get a decent upload speed). If there is really no other way we would consider it though, but I'd like to look alternatives first.

Would it be a solution if we'd package the toolchain in a .deb package with the right dependencies declared? That would at least avoid building it twice.

glimmer

  • *
  • Posts: 119
Re: Can't compile the with the Toolchain.
« Reply #17 on: December 15, 2013, 09:24:48 pm »
Someone on IRC also had problems with libtool not being able to locate files. It's strange it doesn't build everywhere, since it builds fine for me on both openSUSE and Debian. Can you post the contents of one of the .la files? (they're text files)
You missed your window. I wiped the toolchain build directory yesterday. It's sitting on a relatively small SSD that is also the boot volume for that machine, and I needed the space back. :)
Did Ubuntu drop only the bulk package or all 32-bit packages? Since all that the toolchain should need is a 32-bit libc.
There is no longer a metapackage called "ia32-libs". There are still i386 packages denoted by :i386, but I really wouldn't count on those forever.
I'm not eager to add a 64-bit toolchain to the release, since it would lengthen the time it takes to make a release considerably
I can't speak for everyone else, but maybe a switch to an amd64 toolchain? I haven't installed an i386 build of Linux--or any other OS--in a very long time. That's at home or at work.
Would it be a solution if we'd package the toolchain in a .deb package with the right dependencies declared? That would at least avoid building it twice.
It would help a bit, but I'm resolutely against supporting i386 until the end of time. If there's still people installing i386 Linux on amd64 machines, I've never met them. It's already been a decade from introduction, and it's been about six to seven years since every major distro got fully working, optimized amd64 builds of everything.

This is where my dev machine is now, and I'd like to keep it that way:
Code: [Select]
localhost ~ [0]# uname -p
x86_64
localhost ~ [0]# dpkg -l | grep i386 | wc -l
0

sphinxtar

  • Posts: 1
    • Fullsack
Re: Can't compile the with the Toolchain.
« Reply #18 on: January 03, 2014, 08:37:26 pm »
I did a full face plant into this issue running amd64 gentoo no-multilibs, build will not complete, libtool just loses it's mind and spews nonexisting nonsense for paths. My only path forward after many weeks of struggling was to buy a new boot disk and build from scratch with 32bit support x86_64. Created a locally mounted partition on /opt instead of a link and built sweetly in a flash yesterday following directions here; https://github.com/gcwnow/buildroot/wiki Sorry this isn't helping much, my condolences. There were a few other reasons and things I missed in pure 64, like quake 4 and the android emu tools, the world is just not ready yet.
« Last Edit: January 03, 2014, 09:09:33 pm by sphinxtar »

 

Post a new topic