User forums > Using Code::Blocks

Avr-gcc project on x86_64 and gnu/stubs-32.h file

(1/5) > >>

Difool:
Hi !

I'm new user of Code::Blocks and i started with avr-gcc project.
My project compile fine in command line (not with Code::Blocks) with my custom Makefile.

I've trying to copy out this Makefile in Code::Blocks but when i compile, i've this error :

--- Code: ---/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
--- End code ---
I've trying with my custom Makefile (By checking « This is a custom Makefile » in Project properties) but i've the same error.

I think that installing the package "glibc-devel.i686" can solve the problem but why Code: Blocks would need this package which compile fine in command line ?

Thanks

Freem:
Should your project normally need it?
If yes, check directories.

Else, if you check "use a custom makefile" in C::B's project, do it work?

If yes, there is a problem with the configuration of your project.
I think you can look near included libs, maybe the assistant insert "gnu/stubs-32.h" ?

Difool:

--- Quote from: Freem on August 10, 2011, 02:46:23 pm ---Should your project normally need it?
If yes, check directories.

--- End quote ---
No, because it works outside Code::Blocks

With my custom Makefile, it don't need stubs-64.h either (So my project don't need stubs.h ...)
(I've tried to rename stubs-64.h to stubs-64.h.old and to compile with custom Makefile and it works)


--- Quote from: Freem on August 10, 2011, 02:46:23 pm ---Else, if you check "use a custom makefile" in C::B's project, do it work?

--- End quote ---
Yes


--- Quote from: Freem on August 10, 2011, 02:46:23 pm ---If yes, there is a problem with the configuration of your project.
I think you can look near included libs, maybe the assistant insert "gnu/stubs-32.h" ?

--- End quote ---

Here is the cbp file of my project, you can see it have no mention of any stubs header

oBFusCATed:
Read this: http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_troubleshoot_an_compiler_problem.3F and enable full logging.
Then inspect the commands and try them in a terminal to see, which flag or option causes this behaviour.

Difool:
Ok, it works when I remove the « /usr/include » path in Global Compiler Settings -> GNU AVR GCC Compiler -> Search Directories -> Compiler.

This path wasn't added by me, it's the default config.
Is this path useful for anything ?

Navigation

[0] Message Index

[#] Next page