On Thu, Jul 4, 2013 at 7:19 PM, Kim wrote:
> On 2013/07/05 3:42, Earnie Boyd wrote:
>> On Thu, Jul 4, 2013 at 1:54 PM, Kim wrote:
>>> On 2013/07/05 0:42, Earnie Boyd wrote:
>>>> On Wed, Jul 3, 2013 at 5:33 PM, Kim wrote:
>>>>>> It chugs along until it gets to libtool where again BINDIR has the wrong value.
>>>>>> What version of MSYS are you using? Provide the output of ``uname -a''.
>>>>> $ uname -a
>>>>> MINGW32_NT-6.1 KIM-PC 1.0.18(0.48/3/2) 2012-11-21 22:34 i686 Msys
>>>> Hmm.. From the MSYS shell give me the output of the ``set'' command.
>>>> Something is in your environment that is causing this BINDIR issue.
>>> Kim@... /c
>>> $ set
>> Ok, thanks. Your PATH is a bit unsightly. Let's try this experiment.
>> $ export PATH=.:/mingw/bin:/bin
>> $ cd /path/containing/binutils-2.23.1
>> $ rm -rf bintuils-2.23.1
>> $ tar axf /path/to/binutils-2.23.1.tar.gz
>> $ # or whatever the archive tar name is compressed with.
>> $ mkdir bld
>> $ cd bld
>> $ ../bintuils-2.23.1/configure --prefix=/mingw
>> $ make
> Same result with incorrect BINDIR, I pastebinned the output while
> following your instructions in case you notice something I didn't.
I see some things odd, I'll mention two but need more time to study further.
I do see you export PATH correctly so why is the script is looking in
/usr/local/bin, I don't know. I would have expected both of these to
have been found in /bin.