undefined reference to '__mulhi3' In function 'vfprintf': and 'calloc'

[Ralphxyz]

Yes every tab has been inspected!

All I am trying to do is use a default install of Code::Blocks, hard to believe I am the only one to see this stuff.

Thanks for all of the help it is really appreciated.

Ralph

[Jenna]

Please attach you project filke and the default.conf from $APPDATA$\codeblocks\ , so they can be inspected to find the reason for you issue.

[Ralphxyz]

The default.conf is in the project folder.

Ralph

[Ralphxyz]

In looking at the default.conf I see:



Should I change that to the newer Toolchain C:\WinAVR-20100110?

Where is the -L flag set?

Ralph

[Jenna]

Yes every tab has been inspected!

This can not be true !
Or you have absolutely no clue of what libraries are and what a linker/compiler searchpath can be.
In this case you should read a good book/tutorial, that explains the basics of compiler/linker usage (this is not the correct website/forum for such basic stuff, sorry) and read the C::B manual.

All I am trying to do is use a default install of Code::Blocks, hard to believe I am the only one to see this stuff.

It can not be the default install, because there are several settings in the global options of the avrgcc toolchain, which are obviously wrong.

Note: neither headers (*.h), nor sources (*.c in your case) nor object files (*.o in this case) are libraries and the global linker searchdir points to the wrong compiler installation.

[LETARTARE]

In looking at the default.conf I see an big error :

Code

<LIBRARY_DIRS>
    <str>
        <![CDATA[C:\WinAVR-20090313\avr\lib;]]>
    </str>
</LIBRARY_DIRS>

also in "C::B" go

"Settings-> Global Variables -> Current variable"

choose "avr" then delete the contents of the box "lib", then exit and restart "C: B".
The wrong path should no longer appear in your "default.conf."
cordially.

[Jenna]

In looking at the default.conf I see an big error :

Code

<LIBRARY_DIRS>
    <str>
        <![CDATA[C:\WinAVR-20090313\avr\lib;]]>
    </str>
</LIBRARY_DIRS>

also in "C::B" go

"Settings-> Global Variables -> Current variable"

choose "avr" then delete the contents of the box "lib", then exit and restart "C: B".
The wrong path should no longer appear in your "default.conf."
cordially.

It's a linker search path of the avr compiler and not a global variable !

[LETARTARE]

I think it's time for me to go to sleep !!!!
'Jens' in quite right.
In C::B go

Settings-> Compiler-> Compiler GNU AVR GCC-> Search directories-> Linker

this time you should find the old path

C:\WinAVR-20090313\avr\lib

to remove.

Sorry for the hasty response.

[Ralphxyz]

Oh didn't I mention that not only am I new to Code::Blocks but that I hardly know what I am doing.

I just use programs I try to know as little as possible about anything.

I just do the install and then expect to use it.

The reason I have the .c,.h,and .o files in the "Linker settings" is because otherwise they are not found from my #includes.

So this works, now tell the correct way to "include" files.

In C::B go
Quote
Settings-> Compiler-> Compiler GNU AVR GCC-> Search directories-> Linker
this time you should find the old path
Quote
C:\WinAVR-20090313\avr\lib
to remove.

Nope

Yes every tab has been inspected!
This can not be true !

But it is true true I have looked at every tab, and yes it is true that I probable could know more about things
but do I really need to just to run a default install of Code::Blocks?

I am willing to bet that something about Windows 8 x64 is helping to mess things up.

But again thank you everybody for the help.

Ralph

[stahta01]

The tab Compiler IS NOT that same tab as Linker.

Tim S.

[Jenna]

I just use programs I try to know as little as possible about anything.
[...]
But it is true true I have looked at every tab, and yes it is true that I probable could know more about things
but do I really need to just to run a default install of Code::Blocks?

You try to do something special (embedded programming), what will (most likely) bring you much more problems, than just developping for your working system (or other pc's).

But if you state you are not willing to learn, you will never be able to do any serious programming and you are wasting the time of many other people.

I will lock this topic now and ban you for a week.
Come back if you are at least willing to find a solution yourself.