Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
export PREFIX=/usr/local/cross
export TARGET=i586-elf
cd /usr/src
mkdir build-binutils
cd /usr/src/build-binutils
../binutils-x.xx/configure --target=$TARGET --prefix=$PREFIX --disable-nls
make all
make install
/bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../binuti
ls-2.19.1/bfd -I. -D__USE_MINGW_FSEEK -I. -I../../binutils-2.19.1/bfd -I../..
/binutils-2.19.1/bfd/../include -W -Wall -Wstrict-prototypes -Wmissing-proto
types -Wno-format -Werror -g -O2 -D__USE_MINGW_ACCESS -c -o archive.lo ../../bin
utils-2.19.1/bfd/archive.c
./libtool: line 2258: cygpath: command not found
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../binutils-2.19.1/bfd -I. -D__U
SE_MINGW_FSEEK -I. -I../../binutils-2.19.1/bfd -I../../binutils-2.19.1/bfd/../in
clude -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wno-format -Werror -g -
O2 -D__USE_MINGW_ACCESS -c "" -o archive.o
gcc.exe: error: : No such file or directory
gcc.exe: fatal error: no input files
compilation terminated.
make[3]: *** [archive.lo] Error 1
make[3]: Leaving directory `/usr/src/build-binutils/bfd'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/usr/src/build-binutils/bfd'
make[1]: *** [install-bfd] Error 2
make[1]: Leaving directory `/usr/src/build-binutils'
make: *** [install] Error 2
/x.sh: line 8: ../gcc-4.5.0/configure: No such file or directory
make: *** No rule to make target `all-gcc'. Stop.
make: *** No rule to make target `install-gcc'. Stop.
i am getting the same error even for the diff binutils version,i have tried binutils-2.19.1, 2.22.0, 2.23.1
so what can be the problem ??
also my mingw's gcc compiler version is 4.6.2
From a quick google, the 'libtool ... cygpath: command not found' error seems to be a common occurrence with older versions of msys - the only recommended solutions appear to be either not to try building whatever you are trying to build as a shared library or to upgrade your msys version. Are you using a particularly old msys?
That looks like you are not providing the exact commands you use to build, could you provide those, if you still have the problem? I suspect that the configure script thinks its running under Cygwin. Do you have (or have had) Cygwin installed? Perhaps there are some environmental variables around, type 'env' in your bash and show the results here. Try passing the correct --build=whatever-msys-mingw-triple to help configure figure out what platform it is running on.
Not using a several years old binutils will probably help as well.
"Certainly avoid yourself. He is a newbie and might not realize it. You'll hate his code deeply a few years down the road." - Sortie
[ My OS ] [ VDisk/SFS ]
i have tried the disable-shared and make configure-host commands but still the result is same, the same error and annoying part is i am not able to get info about this error on google
That looks like you are not providing the exact commands you use to build, could you provide those, if you still have the problem? I suspect that the configure script thinks its running under Cygwin. Do you have (or have had) Cygwin installed? Perhaps there are some environmental variables around, type 'env' in your bash and show the results here. Try passing the correct --build=whatever-msys-mingw-triple to help configure figure out what platform it is running on.
no i dont have cygwin installed.
these are the result for the env command
export PREFIX=/usr/local/cross
export TARGET=i586-elf
cd /usr/src/build-binutils
../binutils-2.19.1/configure --target=$TARGET --prefix=$PREFIX --disable-nls --disable-shared -disable-libssp --disable-multilib --disable-werror
make configure-host
make
make install
cd /usr/src/build-gcc
export PATH=$PATH:$PREFIX/bin
../gcc-4.5.0/configure --target=$TARGET --prefix=$PREFIX --disable-nls --enable-languages=c --without-headers
make all-gcc
make install-gcc
above is the script that solved my problem and one thing should be kept in mind that the whole script should be executed at one go as it has caused some problems to me
I also faced the same error. But the above solution is not working for me. Getting the same error again.
But as said in the below thread executing the below code after configure making things correct. If this the proposed one is not working, you can try this.