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

[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 Select Expand

/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
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]

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

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)

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

Yes

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" ?

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 ?

[Jenna]

It's not in the default config of C::B !
I don't have it in my clean "GNU AVR GCC Compiler" settings.

So removing it should be save.

[Difool]

It's not in the default config of C::B !
I don't have it in my clean "GNU AVR GCC Compiler" settings.

So removing it should be save.

I confirm is it the default config of Code::Blocks. At least on Fedora 15 and x86_64.
I just to test on another machine with a fresh install of this distribution.
Maybe a « wrong » rpm package ...

[oBFusCATed]

I don't have it in the defaults. (self compiled on centos)
Could you check if you avr-project-wizard is not doing it wrong?

[Difool]

Could you check if you avr-project-wizard is not doing it wrong?

How ?

[oBFusCATed]

Choose the wizard -> right click -> edit script

[Difool]

Choose the wizard -> right click -> edit script

I've seen nothing strange here.

But, here, you can see my ~/.codeblocks/default.conf file.
See at lines 728-732.

[Jenna]

Choose the wizard -> right click -> edit script

I've seen nothing strange here.

But, here, you can see my ~/.codeblocks/default.conf file.
See at lines 728-732.

Please close C::B and rename the default.conf.
Than restart C::B, so the configuration is rebuild from scratch and check the "Search directories".

[Difool]

Please close C::B and rename the default.conf.
Than restart C::B, so the configuration is rebuild from scratch and check the "Search directories".

/usr/include always appear in the search directory

[Difool]

I've just to test on another linux distribution (Ubuntu 11.04 x86_64).
And it's have the same problem : the /usr/include path is, by default, in the « Search Directory » for the AVR GCC Compiler.

So the problem is not with Fedora package but with Code::Block default settings

[oBFusCATed]

What happens, when you:
1. stop codeblocks
2. delete ~/.codeblocks/default.conf
3. start codeblocks

Do you see the same problem?