Mr. jhb50.

This morning i started with your excellent compile guide and ran into a few issues.

In MSys i’m stuck now, i started 3x from the start to be sure i did everything correct.

cd liba52/
./configure –host=powerpc-eabi –prefix=”${DEVKITPRO}/portlibs/ppc” –libdir=”${DEVKITPRO}/portlibs/ppc/lib” –disable-shared

Administrator@BAREBONE /c/wiimc/libs/liba52
$ make

Making all in autotools
make[1]: Entering directory ‘/c/wiimc/libs/liba52/autotools’
make[1]: Nothing to be done for ‘all’
make[1]: Leaving directory ‘/c/libs/liba52/autotools’
Making all in include
make[1]: Entering directory ‘/c/wiimc/libs/liba52/include’
make[1]: Leaving directory ‘/c/libs/liba52/include’
Making all in liba52
make[1]: Entering directory ‘/c/wiimc/libs/liba52/liba52’
/bin/sh ../libtool –mode=link powerpc-eabi-gcc -g -03 -fomit-frame-pointer -prefer-non-pic -o liba52.la -rpath /c/devkitPro/portlibs/ppc/lib -no-undefined bitsrteam.lo imdct.lo bit_allocate.lo parse.lo downmix.lo -lm
rm -fr .libs/liba52.la .libs.liba52.* .libs.liba52.*
ar cru .libs/liba52.la bitstream.o imdct.o bit_allocate.o parse.o downmix.o
../libtool:line 4155: ar: command not found
make[1]: *** [liba52.la] error 127
make[1]: leaving directory ‘/c/wiimc/libs/liba52/liba52’
make: *** [all-recursive] error 1

Then it goes back to Administrator@BAREBONE /c/wiimc/libs/liba52
What can i do to fix this?

@hetfield wrote:

4. In MSys i’m stuck now, i started 3x from the start to be sure i did everything correct.

cd liba52/
./configure –host=powerpc-eabi –prefix=”${DEVKITPRO}/portlibs/ppc” –libdir=”${DEVKITPRO}/portlibs/ppc/lib” –disable-shared

Administrator@BAREBONE /c/wiimc/libs/liba52
$ make

Making all in autotools
make[1]: Entering directory ‘/c/wiimc/libs/liba52/autotools’
make[1]: Nothing to be done for ‘all’
make[1]: Leaving directory ‘/c/libs/liba52/autotools’
Making all in include
make[1]: Entering directory ‘/c/wiimc/libs/liba52/include’
make[1]: Leaving directory ‘/c/libs/liba52/include’
Making all in liba52
make[1]: Entering directory ‘/c/wiimc/libs/liba52/liba52’
/bin/sh ../libtool –mode=link powerpc-eabi-gcc -g -03 -fomit-frame-pointer -prefer-non-pic -o liba52.la -rpath /c/devkitPro/portlibs/ppc/lib -no-undefined bitsrteam.lo imdct.lo bit_allocate.lo parse.lo downmix.lo -lm
rm -fr .libs/liba52.la .libs.liba52.* .libs.liba52.*
ar cru .libs/liba52.la bitstream.o imdct.o bit_allocate.o parse.o downmix.o
../libtool:line 4155: ar: command not found
make[1]: *** [liba52.la] error 127
make[1]: leaving directory ‘/c/wiimc/libs/liba52/liba52’
make: *** [all-recursive] error 1

I get this error too. I solved it dowloading ar command from mingw’s binutils package and copying ar.exe (in /bin folder) to DevKitPro/msys /bin folder. Seems like devkitpro installer forgot it.

Mingw binutils package link: http://sourceforge.net/downloads/mingw/MinGW/BaseSystem/GNU-Binutils/binutils-2.20.51/binutils-2.20.51-1-mingw32-bin.tar.lzma/

@hetfield wrote:

hmmm, i placed the question there

I also looked at the config log.
Strange thing is for example PATH: /mingw/bin (there is no such dir anywhere)
msys batch is mingw, so i thought, change the name msys into mingw :P, but that did’nt change anything.

btw, could it be that no acceptable C compiler found in $PATH means no c compiler in /fribidi? and not in devkitpro?

It means that in your $PATH variable there is no gcc compiler executable. You must change your PATH variable

Please read the devkit forum, he also provided a solution which i didn’t try yet.

the problem was not my installation, but yours 😮
In my attempt to mimic your installs, i screwed up mine, so i have to start from scratch again.
But i’ll save that for a rainy day.

http://www.devkitpro.org/viewtopic.php?f=3&t=2053&sid=f31083634f230f1afbfcf2f74fa36499

    PATH=$DEVKITPPC/bin:$PATH

CPPFLAGS="-mrvl -I$DEVKITPRO/portlibs/ppc/include" LDFLAGS=="-mrvl -L$DEVKITPRO/portlibs/ppc/lib"./configure --host=powerpc-eabi  --disable-shared

Well, i find it interesting that your devkit installation is different from the original.
That is why wintermute suspects yours was faulted.
And i read other posts of you on devkit.org, with some problems you discribed there, it looks like you keep running into problems.
I wonder why.
Did you ever compile anything without errors?

On 3 different computers i did the following:
1. Started from scratch with wiimc, but same thing all over again.
2. I started from scratch with sneek source which was without any problems.

So this strange problem cannot be on my side, there must be something wrong with the code.
And since i am the first to report this here, i doubt that anyone else succeeded.
As a matter a fact, i am the only one who replied here!!!
If (many) others succeeded, there would be at least a few thank you posts, or not?

Just for the fun of it, try your guide again yourself from the beginning, on a PC that never did any compiling stuf.
Remember, everyone who starts from scratch with devkitpro install, do not have the corrections you did on your pc.