'invalid package name' error when building binutils

[Alpha]

Hi,

I am using windows with cygwin and trying to build a cross-compiler.

I have followed the article on the wiki (http://wiki.osdev.org/Cannot_perform_PE ... on-PE_file) as well as other tutorials, but i fail at compiling binutils.

When i try to run make it gives the folowing output:

Code: Select all

make[1]: Entering directory `/d/cygwin/home/build/binutils'
Configuring in ./intl
configure: error: invalid package name: 0
make[1]: *** [configure-intl] Error 1
make[1]: Leaving directory `/d/cygwin/home/build/binutils'
make: *** [all] Error 2

I don't know ho to solve this problem. Hopefully somebody could tell me what to do.


Alpha

[sortie]

Hi, please consider what information we would need to help you. Your error message is kinda weird. Could you give the ./configure line you used and other relevant information?

[dozniak]

Try --disable-nls for starters?

[Alpha]

I am working with cygwin on windows 8 (64bit)

This is what i do:

Code: Select all

~ $ export PREFIX=$HOME/crosscompiler
~ $ export TARGET=i586-elf
~ $ export PATH="$PREFIX/bin:$PATH"
~ $ cd $HOME/build/build/binutils
~/build/build/binutils $ ../binutils-2.23.2/configure --target=$TARGET --prefix="$PREFIX" --disable-nls > conf_out.txt
~/build/build/binutils $ make
make[1]: Entering directory `/d/cygwin/home/build/binutils'
mkdir -p -- ./intl
Configuring in ./intl
configure: error: invalid package name: 0
make[1]: *** [configure-intl] Error 1
make[1]: Leaving directory `/d/cygwin/home/build/binutils'
make: *** [all] Error 2

I dont have a single clue where it goes wrong.

[sortie]

Hi, the cross-compiler tutorial states:

Code: Select all

Configure: error: invalid feature name: nls

If you are using Cygwin, it must be set to use Unix/binary as the file mode. You can set this by running setup.exe and selecting the appropriate mode. 

You wouldn't happen to be encountering that bug?

[Alpha]

Well the installation program doesn't ask me for selecting a filemode. I guess this option is left out in the most recent versions of the installer.

I guess my only option is trying a dual boot with linux.

[dozniak]

> conf_out.txt

Have you actually tried to read this file?

[Alpha]

Yes i did. But it din't provide usefull information for me:

Code: Select all

checking build system type... x86_64-unknown-cygwin
checking host system type... x86_64-unknown-cygwin
checking target system type... i586-pc-elf
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /usr/bin/sed
checking for gawk... gawk
checking to see if cat works as expected... yes
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for gnatbind... no
checking for gnatmake... no
checking whether compiler driver understands Ada... no
checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2
checking for objdir... .libs
checking for PWL_handle_timeout in -lpwl... no
checking for version 0.11 (revision 0 or later) of PPL... no
checking for default BUILD_CONFIG... 
checking for bison... bison -y
checking for bison... bison
checking for gm4... no
checking for gnum4... no
checking for m4... m4
checking for flex... flex
checking for flex... flex
checking for makeinfo... makeinfo
checking for expect... no
checking for runtest... no
checking for ar... ar
checking for as... as
checking for dlltool... dlltool
checking for ld... (cached) /usr/lib/gcc/x86_64-pc-cygwin/4.8.1/../../../../x86_64-pc-cygwin/bin/ld.exe
checking for lipo... no
checking for nm... nm
checking for ranlib... ranlib
checking for strip... strip
checking for windres... windres
checking for windmc... windmc
checking for objcopy... objcopy
checking for objdump... objdump
checking for readelf... readelf
checking for i586-elf-cc... no
checking for i586-elf-gcc... no
checking for i586-elf-c++... no
checking for i586-elf-g++... no
checking for i586-elf-cxx... no
checking for i586-elf-gxx... no
checking for i586-elf-gcc... no
checking for i586-elf-gcj... no
checking for i586-elf-gfortran... no
checking for i586-elf-gccgo... no
checking for i586-elf-ar... no
checking for i586-elf-as... no
checking for i586-elf-dlltool... no
checking for i586-elf-ld... no
checking for i586-elf-lipo... no
checking for i586-elf-nm... no
checking for i586-elf-objdump... no
checking for i586-elf-ranlib... no
checking for i586-elf-readelf... no
checking for i586-elf-strip... no
checking for i586-elf-windres... no
checking for i586-elf-windmc... no
checking where to find the target ar... just compiled
checking where to find the target as... just compiled
checking where to find the target cc... pre-installed
checking where to find the target c++... pre-installed
checking where to find the target c++ for libstdc++... pre-installed
checking where to find the target dlltool... just compiled
checking where to find the target gcc... pre-installed
checking where to find the target gcj... pre-installed
checking where to find the target gfortran... pre-installed
checking where to find the target gccgo... pre-installed
checking where to find the target ld... just compiled
checking where to find the target lipo... pre-installed
checking where to find the target nm... just compiled
checking where to find the target objdump... just compiled
checking where to find the target ranlib... just compiled
checking where to find the target readelf... just compiled
checking where to find the target strip... just compiled
checking where to find the target windres... just compiled
checking where to find the target windmc... just compiled
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether -fkeep-inline-functions is supported... yes
configure: creating ./config.status
config.status: creating Makefile

[sortie]

If possible, I strongly recommend doing osdev from an Unix environment (even if you had to create it yourself ;D). The build instructions and tools are often much easier to build and the community has an easier time helping you.