On Thu, Sep 19, 2013 at 8:11 PM, John E. / TDM wrote:
> On 9/19/2013 4:31 PM, Earnie Boyd wrote:
>>>> On Thu, Sep 19, 2013 at 2:08 PM, John E. / TDM wrote:
>>>>> Looks like this build of GCC has an unrelocated reference to a folder
>>>>> the packager's I: drive.
>> Do you have a trick to remove the reference to the development
> Any one of the following should suffice.
> 1 - Using an MSYS shell, build GCC in a fully "identity-mounted"
> environment, where X:\mingw is mounted as /mingw (X being any Windows drive)
> and whatever directories you build in and get sources from are similarly
> matched. For example, I build with H:\mingw mounted as /mingw and
> H:\crossdev mounted as /crossdev, and place my build directory and sources
> in various subdirectories of H:\crossdev. I believe it also helps to use a
> relative path when executing GCC's configure script, like
> "../src/gcc/configure <options>".
> 2 - Using a Cygwin shell and the above "identity-mount" configuration, build
> a native mingw32 GCC. This is trickier and I haven't done it in a while.
> 3 - Use the attached patch on GCC's source, which makes all paths subject to
> the relocation machinery and removes some unnecessary duplicates.
> 4 - Use a strings editor to alter any broken paths in the final compiler
> executables, removing the drive spec so they begin with merely a forward
Thanks John, I'll remember this for the next release I do.
As for the OP, you seem to have a few options at hand.
1) Remove the mapping of the non-existing drive that I is mapped to.
2) Add the drive that I is mapped to.
3) Edit the GCC binaries and remove the I: from the strings.
4) Build GCC source yourself using the source bundle from mingw-get.