Author Topic: cannot find C:\MinGW\lib: Permission Denied  (Read 16757 times)

Offline Atifhossain

  • Single posting newcomer
  • *
  • Posts: 4
cannot find C:\MinGW\lib: Permission Denied
« on: March 07, 2013, 09:19:51 am »
I downloaded Code Blocks  12.11 , then downloaded the MinGW compiler and also SFML. Then I moved the (SMFL) folder from (SMFL../include ) to (C:/MinGw/include) and also copied all the .a files from (SMFL../lib) to (MinGw/lib). I then compiled and ran a hello world project in Code::Blocks

The build message says :

cannot find C:\MinGW\lib: Permission Denied
What to do ?
« Last Edit: March 07, 2013, 12:09:30 pm by Atifhossain »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13406
    • Travis build status
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7785
    • My Best Post
Re: cannot find C:\MinGW\lib: Permission Denied
« Reply #2 on: March 07, 2013, 10:07:55 am »
I compiled and ran a project in Code::Blocks 12.11.The build message says :

cannot find C:\MinGW\lib: Permission Denied
What to do ?

Simple question, does the folder "C:\MinGW\lib" exist?
Can you open it when not using Code::Blocks?

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline Atifhossain

  • Single posting newcomer
  • *
  • Posts: 4
Re: cannot find C:\MinGW\lib: Permission Denied
« Reply #3 on: March 07, 2013, 12:08:43 pm »

Simple question, does the folder "C:\MinGW\lib" exist?
Can you open it when not using Code::Blocks?

Tim S.

Yea . The folder exist and I CAN open it from outside too.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7785
    • My Best Post
Re: cannot find C:\MinGW\lib: Permission Denied
« Reply #4 on: March 07, 2013, 03:55:16 pm »
What is the path inside Code::Blocks set to for the compiler toolchain?

What is the "message log" output in full compiler logging mode?

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline Atifhossain

  • Single posting newcomer
  • *
  • Posts: 4
Re: cannot find C:\MinGW\lib: Permission Denied
« Reply #5 on: March 07, 2013, 04:13:19 pm »
What is the path inside Code::Blocks set to for the compiler toolchain?

What is the "message log" output in full compiler logging mode?

Tim S.

I moved the MinGW file from Local Disk (C) to Dekstop and changed the corresponding settings in Code Blocks. And yet the same result.
The Path Inside the Code Blocks is set as --   C:\Documents and Settings\HP\Desktop\MinGW  --.
I have no idea as to what do you mean by the second question.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7785
    • My Best Post
Re: cannot find C:\MinGW\lib: Permission Denied
« Reply #6 on: March 07, 2013, 04:23:32 pm »
http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28errors%29#Q:_How_do_I_troubleshoot_a_compiler_problem.3F

What is the path inside Code::Blocks set to for the compiler toolchain?

What is the "message log" output in full compiler logging mode?

Tim S.

I moved the MinGW file from Local Disk (C) to Dekstop and changed the corresponding settings in Code Blocks. And yet the same result.
The Path Inside the Code Blocks is set as --   C:\Documents and Settings\HP\Desktop\MinGW  --.
I have no idea as to what do you mean by the second question.


Read the stuff people post or quit posting on this site!

http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28errors%29#Q:_How_do_I_troubleshoot_a_compiler_problem.3F

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline Atifhossain

  • Single posting newcomer
  • *
  • Posts: 4
Re: cannot find C:\MinGW\lib: Permission Denied
« Reply #7 on: March 08, 2013, 01:47:31 pm »
Seems like RE-INSTALLING fixed the problem