Re: [Mingw-users] Binutils make failure

[Kim <sol...@gm...>]

Thanks very much for your response.

Here is the complete process I'm using starting from a freshly unpacked 
binutils src dir:
http://pastebin.com/9Pur8WhA

The binutils readme suggests that it should be fine to run configure 
from the same directory.

You're right about DBINDIR, after checking where these directories are 
being assigned in the makefile I found

-DBINDIR='"$(bindir)"'
bindir = ${exec_prefix}/bin
exec_prefix = ${prefix}
prefix = C:/MinGW

As far as I can tell that should work properly but the slashes seem to 
be ignored for some reason.

Hardcoding DBINDIR to 'C:/MinGW/bin/ gets me further in the build but 
more errors related to the incorrectly handled slashes pop up later.



On 2013/07/03 19:24, Earnie Boyd wrote:
> On Tue, Jul 2, 2013 at 3:07 PM, Kim wrote:
>> I'm attempting to build binutils 2.23.1 (downloaded here:
>> http://sourceforge.net/projects/mingw/files/MinGW/Base/binutils/) from
>> the mingw shell on windows.
>>
> Brave soul.
>
>> I installed the mgwport package (after autoconf and automake) and tried
>> that first.
>>
> Even braver still.
>
>> Kim@Kim-PC /c/binutils-2.23.1-1-mingw32-src
>> $ mgwport binutils-2.23.1-1.mgwport all
>>   >>> Preparing binutils-2.23.1-1
>>   >>> Unpacking source binutils-2.23.1.tar.bz2
>>   >>> Preparing working source directory
>> *** Info: applying patch binutils-2.23.1-1.mgw.patch:
>> patching file MINGW-PATCHES/binutils.README
>> *** Info: applying patch binutils-2.23.1-1.src.patch:
>> patching file config.rpath
>>   >>> Compiling binutils-2.23.1-1
>>
>> It seems to freeze up at that point. Here is the mwgport log:
>>
> Don't know why.
>
>> mgwport 0.10.6
>>
>> PF = binutils-2.23.1-1
>> S = /c/binutils-2.23.1-1-mingw32-src/binutils-2.23.1-1/src/binutils-2.23.1
>> B = /c/binutils-2.23.1-1-mingw32-src/binutils-2.23.1-1/build
>> D = /c/binutils-2.23.1-1-mingw32-src/binutils-2.23.1-1/inst
>> C =
>> T = /c/binutils-2.23.1-1-mingw32-src/binutils-2.23.1-1/temp
>> CBUILD = i686-pc-mingw32
>> CHOST = i686-pc-mingw32
>> CTARGET = i686-pc-mingw32
>> CC = gcc
>> CFLAGS = -g -O2 -pipe -mms-bitfields
>> CPPFLAGS =
>> CXX = g++
>> CXXFLAGS = -g -O2 -pipe -mms-bitfields
>> F77 = gfortran
>> FFLAGS = -g -O2 -pipe
>> FC = gfortran
>> FCFLAGS = -g -O2 -pipe -mms-bitfields
>> GCJ = gcj
>> GCJFLAGS = -g -O2 -pipe -mms-bitfields
>> OBJC = gcc
>> OBJCFLAGS = -g -O2 -pipe -mms-bitfields
>> OBJCXX = g++
>> OBJCXXFLAGS = -g -O2 -pipe -mms-bitfields
>> LDFLAGS =
>> LIBS =
>> MAKEOPTS = -j1
>>
>> So after that I gave up on mgwport and headed into the binutils origsrc
>> directory created by mgwport and tried a manual configure and make. The
>> configuration process is successful but make fails here:
>>
> Ah, so this is somewhat what I would've done from the start after
> realizing the patch file was just adding a README file.  One word of
> caution, use a build directory outside of the source directory to
> execute the configure file.  Some packages do not like being
> configured within the source.  Some packages do not like being
> configured outside the source.  It is always best to try first
> configuring outside the source.
>
>> C:/MinGW/msys/1.0/bin/sh.exe ./libtool --tag=CC   --mode=compile gcc
>> -DHAVE_CONF
>> IG_H -I. -D__USE_MINGW_FSEEK    -I. -I. -I./../include -DHAVE_i386pe_vec
>> -DHAVE
>> _i386pei_vec -DHAVE_bfd_elf32_i386_vec
>> -DHAVE_bfd_elf32_little_generic_vec -DHAV
>> E_bfd_elf32_big_generic_vec  -DBINDIR='"C;C:MinGWbin"'  -W -Wall
> The BINDIR value is strange; it should be C:/MinGW/bin.
>
>> -Wstrict-protot
>> ypes -Wmissing-prototypes -Wshadow -Wno-format -Werror -g -O2
>> -D__USE_MINGW_ACCE
>> SS -MT archive.lo -MD -MP -MF .deps/archive.Tpo -c -o archive.lo archive.c
>> Xarchive.Tpo -c -o archive.lo archive.lo
>> libtool: compile: warning: libobj name `archive.Tpo -c -o archive.lo
>> archive.lo'
>>    may not contain shell special characters.
>> rm: invalid option -- c
> libtool is hiding something.  Why is it giving this issue about rm?
>
>> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -D__USE_MINGW_FSEEK -I. -I.
>> -I./../in
>> clude -DHAVE_i386pe_vec -DHAVE_i386pei_vec -DHAVE_bfd_elf32_i386_vec
>> -DHAVE_bfd_
>> elf32_little_generic_vec -DHAVE_bfd_elf32_big_generic_vec
>> "-DBINDIR=\\C;C:MinGWb
>> in\" -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow
> Again the BINDIR is strange.
>
>> -Wno-format -Wer
>> ror -g -O2 -D__USE_MINGW_ACCESS -MT archive.lo -MD -MP -MF
>> .deps/archive.Tpo -c
>> -o archive.lo archive.c" -o archive.Tpo -c -o archive.lo archive.o
>> gcc.exe: Error: archive.o: No such file or directory
>> gcc.exe: There is no input file: fatal error
>> rm: invalid option -- c
>> Try `rm --help' for more information.
>> make[4]: *** [archive.lo] Error 1
>> make[4]: Leaving directory
>> `c:/binutils-2.23.1-1-mingw32-src/binutils-2.23.1-1/o
>> rigsrc/binutils-2.23.1/bfd'
>> make[3]: *** [all-recursive] Error 1
>> make[3]: Leaving directory
>> `c:/binutils-2.23.1-1-mingw32-src/binutils-2.23.1-1/o
>> rigsrc/binutils-2.23.1/bfd'
>> make[2]: *** [all] Error 2
>> make[2]: Leaving directory
>> `c:/binutils-2.23.1-1-mingw32-src/binutils-2.23.1-1/o
>> rigsrc/binutils-2.23.1/bfd'
>> make[1]: *** [all-bfd] Error 2
>> make[1]: Leaving directory
>> `c:/binutils-2.23.1-1-mingw32-src/binutils-2.23.1-1/o
>> rigsrc/binutils-2.23.1'
>> make: *** [all] Error 2
>>
>> It looks like a problem with forward slashes not being handled correctly
>> on a switch (the "Xarchive.Tpo" part). I investigated the makefile in
>> the bfd directory and this seems to be the problem part:
> I think you mean back slashes; BINDIR in the Makfile appears to be wrong.
>
>> .c.o:
>>       $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $<
>>       $(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
>> #    source='$<' object='$@' libtool=no \
>> #    DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) \
>> #    $(COMPILE) -c $<
>>
>> .c.obj:
>>       $(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@
>> `$(CYGPATH_W) '$<'`
>>       $(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
>> #    source='$<' object='$@' libtool=no \
>> #    DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) \
>> #    $(COMPILE) -c `$(CYGPATH_W) '$<'`
>>
> What is the value of COMPILE?
>
>> .c.lo:
>>       $(LTCOMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $<
>>       $(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Plo
>> #    source='$<' object='$@' libtool=yes \
>> #    DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) \
>> #    $(LTCOMPILE) -c -o $@ $<
>>
> What is the value of LTCOMPILE?
>
>
> Also give us what you gave to configure as arguments.  We cannot
> determine from what you've given us the issue.
>