OSDev.org

The Place to Start for Operating System Developers
It is currently Wed Apr 17, 2024 7:01 pm

All times are UTC - 6 hours




Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: Getting Error while making binutils.
PostPosted: Tue Jul 04, 2017 10:09 pm 
Offline

Joined: Tue Jul 04, 2017 9:32 pm
Posts: 2
Hello,
I'm trying to build binutils and I am getting an error when I run make. I am using binutils version 2.27 and I am using Cygwin on Windows 10 64bit.

My Configure Output is:
Code:
checking build system type... x86_64-unknown-cygwin
checking host system type... x86_64-unknown-cygwin
checking target system type... i686-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 whether g++ accepts -static-libstdc++ -static-libgcc... 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 isl 0.16, 0.15, or deprecated 0.14... yes
checking for isl 0.16 or 0.15... no
checking for default BUILD_CONFIG...
checking for --enable-vtable-verify... no
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/5.4.0/../../../../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 i686-elf-cc... no
checking for i686-elf-gcc... no
checking for i686-elf-c++... no
checking for i686-elf-g++... no
checking for i686-elf-cxx... no
checking for i686-elf-gxx... no
checking for i686-elf-gcc... no
checking for i686-elf-gcj... no
checking for i686-elf-gfortran... no
checking for i686-elf-gccgo... no
checking for i686-elf-ar... no
checking for i686-elf-as... no
checking for i686-elf-dlltool... no
checking for i686-elf-ld... no
checking for i686-elf-lipo... no
checking for i686-elf-nm... no
checking for i686-elf-objcopy... no
checking for i686-elf-objdump... no
checking for i686-elf-ranlib... no
checking for i686-elf-readelf... no
checking for i686-elf-strip... no
checking for i686-elf-windres... no
checking for i686-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 objcopy... 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
configure: creating ./config.status
config.status: creating Makefile


Here is the output of Make, where the error is occurring:
Code:
make[1]: Entering directory '/home/Andrew Erhardt/src/build-binutils'
mkdir -p -- ./libiberty
Configuring in ./libiberty
/home/Andrew: /home/Andrew: Is a directory
make[1]: *** [Makefile:8003: configure-libiberty] Error 1
make[1]: Leaving directory '/home/Andrew Erhardt/src/build-binutils'
make: *** [Makefile:854: all] Error 2


Top
 Profile  
 
 Post subject: Re: Getting Error while making binutils.
PostPosted: Tue Jul 04, 2017 10:14 pm 
Offline
Member
Member
User avatar

Joined: Tue Mar 06, 2007 11:17 am
Posts: 1225
Try using a directory without spaces in the name, or escape it somehow. Only half of your directory name is being used as two separate commands.

_________________
Live PC 1: Image Live PC 2: Image

YouTube:
http://youtube.com/@AltComp126/streams
http://youtube.com/@proyectos/streams

http://master.dl.sourceforge.net/projec ... 7z?viasf=1


Top
 Profile  
 
 Post subject: Re: Getting Error while making binutils.
PostPosted: Tue Jul 04, 2017 11:51 pm 
Offline

Joined: Tue Jul 04, 2017 9:32 pm
Posts: 2
~ wrote:
Try using a directory without spaces in the name, or escape it somehow. Only half of your directory name is being used as two separate commands.

That was the issue. Thanks!


Top
 Profile  
 
 Post subject: Re: Getting Error while making binutils.
PostPosted: Fri Jul 07, 2017 12:34 pm 
Offline
Member
Member

Joined: Mon Jan 03, 2011 6:58 pm
Posts: 283
andrewerhardt wrote:
~ wrote:
Try using a directory without spaces in the name, or escape it somehow. Only half of your directory name is being used as two separate commands.

That was the issue. Thanks!


Also, don't use cygwin, use Bash for Windows since you have windows 10.

- Monk


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC - 6 hours


Who is online

Users browsing this forum: Bing [Bot] and 259 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group