Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Thread

Libary problem with Hitop5 from Hitex

Libary problem with Hitop5 from Hitex

2006-05-31 by geri882

Hi,
I have a problem with including the stdio.h into my project in 
Hitop5 for programming a LPC controller.
Hitop5 is the programming IDE from Hitex and uses the GNU compiler.
I need the the libary because of the sprintf command.
The libary is included with:
#include <stdio.h>
and the syntax of the sprintf command is 100% correct.
So there must be a problem with the including or the use of libary 
header files.
Here for example some warnings from the built process:
********************************************************
(C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-elarm-hitex-elf-ld: 
Warning: C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-
elf\lib/libc.a(sprintf.o) does not support interworking, 
whereas .\objects\2138LCD.elf does
arm-hitex-elf-ld: Warning: C:\Programme\Hitex\GnuToolPackageArm\arm-
hitex-elf\lib/libc.a(vfprintf.o) does not support interworking, 
whereas .\objects\2138LCD.elf does
...

C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-elf\lib/libc.a
(vfprintf.o)(.text+0xb54): In function `_vfprintf_r':
../../../../../../GccSources/newlib-
1.13.0/newlib/libc/stdio/vfprintf.c:821: undefined reference to 
`__ltdf2'
...

C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-elf\lib/libc.a
(mprec.o)(.text+0xbdc): In function `_mprec_log10':
../../../../../../GccSources/newlib-
1.13.0/newlib/libc/stdlib/mprec.c:983: undefined reference to 
`__muldf3'
...
**************************************************************
There are a lot more similar warnings or errors like above.

Has anyone an idea or can help? Or is anyone working with Hitop 5 
and doesn't have this problem with including libary files?

It would also be helpful,if there are functions which can change 
integers or floats into char(in decimal, hex and binary syntax)
Thanks for helping
Bye Bye
Gerald

Re: [lpc2000] Libary problem with Hitop5 from Hitex

2006-06-01 by Tom Walsh

geri882 wrote:

>Hi,
>I have a problem with including the stdio.h into my project in 
>Hitop5 for programming a LPC controller.
>Hitop5 is the programming IDE from Hitex and uses the GNU compiler.
>I need the the libary because of the sprintf command.
>The libary is included with:
>#include <stdio.h>
>and the syntax of the sprintf command is 100% correct.
>So there must be a problem with the including or the use of libary 
>header files.
>Here for example some warnings from the built process:
>********************************************************
>(C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-elarm-hitex-elf-ld: 
>Warning: C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-
>elf\lib/libc.a(sprintf.o) does not support interworking, 
>whereas .\objects\2138LCD.elf does
>arm-hitex-elf-ld: Warning: C:\Programme\Hitex\GnuToolPackageArm\arm-
>hitex-elf\lib/libc.a(vfprintf.o) does not support interworking, 
>whereas .\objects\2138LCD.elf does
>...
>
>C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-elf\lib/libc.a
>(vfprintf.o)(.text+0xb54): In function `_vfprintf_r':
>../../../../../../GccSources/newlib-
>1.13.0/newlib/libc/stdio/vfprintf.c:821: undefined reference to 
>`__ltdf2'
>...
>
>C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-elf\lib/libc.a
>(mprec.o)(.text+0xbdc): In function `_mprec_log10':
>../../../../../../GccSources/newlib-
>1.13.0/newlib/libc/stdlib/mprec.c:983: undefined reference to 
>`__muldf3'
>...
>**************************************************************
>There are a lot more similar warnings or errors like above.
>
>Has anyone an idea or can help? Or is anyone working with Hitop 5 
>and doesn't have this problem with including libary files?
>
>It would also be helpful,if there are functions which can change 
>integers or floats into char(in decimal, hex and binary syntax)
>Thanks for helping
>Bye Bye
>Gerald
>
>
>  
>

strings libgcc.a | grep __muldf3
__muldf3
__muldf3
__muldf3
__muldf3
__muldf3
__muldf3
__muldf3


Hmm, looks like you have some problem finding libgcc.a to link 
against?   Probably a poorly constructed link sequence when specifying 
libs and their order of linking.

'ld' is a single pass linker, it is not a multi-pass linker as you may 
be used to in the windows world.  Think of it as a 'link-ahead', you 
have an object file with an unsatisifed reference, the linker will 
resolve that reference in the subsequently named libs / object files.  
Any previous mention of that name, prior to the reference, is ignored.

This allows you to override library references with your own wrapper 
code, etc, etc.

TomW




>
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>
>  
>


-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

Re: Libary problem with Hitop5 from Hitex

2006-06-01 by geri882

--- In lpc2000@yahoogroups.com, Tom Walsh <tom@...> wrote:
>
> geri882 wrote:
> 
> >Hi,
> >I have a problem with including the stdio.h into my project in 
> >Hitop5 for programming a LPC controller.
> >Hitop5 is the programming IDE from Hitex and uses the GNU 
compiler.
> >I need the the libary because of the sprintf command.
> >The libary is included with:
> >#include <stdio.h>
> >and the syntax of the sprintf command is 100% correct.
> >So there must be a problem with the including or the use of 
libary 
> >header files.
> >Here for example some warnings from the built process:
> >********************************************************
> >(C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-elarm-hitex-elf-
ld: 
> >Warning: C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-
> >elf\lib/libc.a(sprintf.o) does not support interworking, 
> >whereas .\objects\2138LCD.elf does
> >arm-hitex-elf-ld: Warning: 
C:\Programme\Hitex\GnuToolPackageArm\arm-
> >hitex-elf\lib/libc.a(vfprintf.o) does not support interworking, 
> >whereas .\objects\2138LCD.elf does
> >...
> >
> >C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-elf\lib/libc.a
> >(vfprintf.o)(.text+0xb54): In function `_vfprintf_r':
> >../../../../../../GccSources/newlib-
> >1.13.0/newlib/libc/stdio/vfprintf.c:821: undefined reference to 
> >`__ltdf2'
> >...
> >
> >C:\Programme\Hitex\GnuToolPackageArm\arm-hitex-elf\lib/libc.a
> >(mprec.o)(.text+0xbdc): In function `_mprec_log10':
> >../../../../../../GccSources/newlib-
> >1.13.0/newlib/libc/stdlib/mprec.c:983: undefined reference to 
> >`__muldf3'
> >...
> >**************************************************************
> >There are a lot more similar warnings or errors like above.
> >
> >Has anyone an idea or can help? Or is anyone working with Hitop 5 
> >and doesn't have this problem with including libary files?
> >
> >It would also be helpful,if there are functions which can change 
> >integers or floats into char(in decimal, hex and binary syntax)
> >Thanks for helping
> >Bye Bye
> >Gerald
> >
> >
> >  
> >
> 
> strings libgcc.a | grep __muldf3
> __muldf3
> __muldf3
> __muldf3
> __muldf3
> __muldf3
> __muldf3
> __muldf3
> 
> 
> Hmm, looks like you have some problem finding libgcc.a to link 
> against?   Probably a poorly constructed link sequence when 
specifying 
> libs and their order of linking.
> 
> 'ld' is a single pass linker, it is not a multi-pass linker as you 
may 
> be used to in the windows world.  Think of it as a 'link-ahead', 
you 
> have an object file with an unsatisifed reference, the linker will 
> resolve that reference in the subsequently named libs / object 
files.  
> Any previous mention of that name, prior to the reference, is 
ignored.
> 
> This allows you to override library references with your own 
wrapper 
> code, etc, etc.
> 
> TomW

It's possible that, the linker makes a problem and can't include an 
assembler libary. But the path in the startupcode generator for 
assembler libarys ist right. 
And I have no idea where it's possible to make those adjustments in 
Hitop.
HAs anyone an idea whos also working with Hitop?

I have this problem, when the sprintf instruction is used. When 
sprintf is commented out I have no problem.
So is the stdio.h libary only included if an istruction of the 
libary is used?

Gerald

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.