User forums > General (but related to Code::Blocks)

TDM's unofficial GCC 4.2.0 for MinGW (now with OpenMP, Fortran and Obj-C)

<< < (19/22) > >>

stahta01:

--- Quote from: dwmcqueen on July 14, 2007, 11:25:44 pm ---Something I noticed - and am having a weird time figuring out how.

I have this version installed to C:\MingW-4.2\.  However, the linker is pulling in libraries from my C:\MingW\lib directory even though it is not specified as a library path (and isn't in an environment variable).  It also pulls in from my C:\MingW-4.2\lib.  Anyone know how to get it to ignore my C:\MingW\lib directory?

--- End quote ---

I have found that in order to avoid that you can not have an X:\MingW on your computer (where X is any of the drives on your computer).

Tim S

TDragon:
What Tim said. :)

Basically, "/mingw/lib" is, by default, hardcoded into the directories to be searched. If someone more knowledgeable about GCC's internal workings than me provides a patch to turn this off, I can certainly apply it to my distributions.

dwmcqueen:
Does it search there before or after the one passed in (in my case C:\MingW-4.2)?

dwmcqueen:
I just wanted to make sure I understood what you said, 20-40 - are you saying we are insane to name our directories C:\MingW-[version] or one would be insane to install it to C:\MingW ?

stahta01:

--- Quote from: dwmcqueen on July 15, 2007, 08:24:16 pm ---I just wanted to make sure I understood what you said, 20-40 - are you saying we are insane to name our directories C:\MingW-[version] or one would be insane to install it to C:\MingW ?

--- End quote ---

I myself consider it best to only install to C:\MinGW or in using multiple installs to make sure C:\MinGW does not exists.

Note: Per my understanding of TDM Directions, when building GCC you should use C:\MinGW. Since I don't use C:\MinGW I think I know why my last try on building MinGW GCC failed. ( About 2 to 3 months ago.)

Tim S

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version