Home / Browse / GCC toolchain for MSP430 / Mail / Archive

GCC toolchain for MSP430

Email Archive: mspgcc-users (read-only)

Re: [Mspgcc-users] internal error: out of range error

From: Wayne Uroda <Wayne.Uroda@gr...> - 2009-06-04 03:42

Thanks for that, most interesting.

 

Do you know if the linker applies this behaviour to .c and .o files as
well? Or just files linked using -l ?

 

- Wayne

 

 

From: Przemek Klosowski [mailto:przemek.klosowski@...] 
Sent: Thursday, 4 June 2009 1:14 PM
To: Wayne Uroda; GCC for MSP430 - http://mspgcc.sf.net
Subject: Re: [Mspgcc-users] internal error: out of range error

 

 

On Tue, Jun 2, 2009 at 9:18 AM, Wayne Uroda <wayne.uroda@...>
wrote:

I meant to say "I am unclear myself what happens when library A needs
library B and vice-versa". Then I wonder if the order matters?


At each point in the link the linker has a list of requested external
symbols. Each library is scanned for those symbols;
if it doesn't provide any, it ends up being ignored. In your case, yes
the order matters, Observe:

cat > bar.c 
bar(){foo();}

cat > foo.c
foo(){bar();}

cat >test.c
main(){foo();}

gcc -c foo.c bar.c
ar qcv libfoo.a foo.o
ar qcv libbar.a bar.o

So, we've created two libraries, calling each other. Now, linking the
wrong way doesn't work:

 gcc -o test test.c -L. -lbar -lfoo
./libfoo.a(foo.o): In function `foo':
foo.c:(.text+0x7): undefined reference to `bar'
collect2: ld returned 1 exit status

but the other way works:

gcc -o test test.c -L. -lfoo -lbar

In other words, you must place them so that the first one will contain
symbols requested by previous code (foo() call in main(), defined in
libfoo.a). Linking in modules from libfoo will place a request for
symbol  bar()  on the list, so that by the time libbar is scanned, they
will be pulled in too. If you put libbar first though, it'll be ignored,
and then libfoo will satisfy the original reference to foo() but it'll
be too late to get bar() from libbar. 

Theoretically, the linker could be doing two passes and remember all
symbols from all libraries, but  the current behavior is faster and
actually useful if you have multiply defined symbols---you can juggle
them by this explicit order
mechanism.

Thread View

Thread	Author	Date
[Mspgcc-users] internal error: out of range error	Douglass, Woodrow <wdouglass@fo...>

Re: [Mspgcc-users] internal error: out of range error

From: Wayne Uroda <Wayne.Uroda@gr...> - 2009-06-02 01:03

Hi Woodrow,

The linker will only bring in an object if it contains an undefined
symbol when it is read on the command line (it reads files left to
right).

The Symbol main gets referenced in libgcc.a(__jump_to_main.o). Unless
you specify otherwise, libgcc.a is linked last by the linker. This means
when you asked it to link libs/libmain.a it did nothing because that
wasn't required at the time.

You can change the link order like this:

msp430-gcc -mmcu=msp430xG4618 -Wl,-Map=./main.map,--cref --output
main.elf newmodule.o libs/libkernel.a libs/libmail.a libs/libversion.a
-lgcc libs/libmain.a

The -lgcc just tells the linker to pull in libgcc.a from its library
path. It will then see that `main' is undefined, and so will link it
next when it sees libmain.a.

I did a small experiment here like this:

#### This has an error:
> msp430-gcc -mmcu= msp430xG4618 main.a
..../libgcc.a(_reset_vector__.o): In function `_reset_vector__':
config/msp430/libgcc.S:(.init+0x38): undefined reference to `main'

#### But this builds fine:
> msp430-gcc -mmcu= msp430xG4618 -lgcc main.a

I am not a guru on this but I think it should work. I am sure if it
doesn't somebody else here will know the answer.

- Wayne

-----Original Message-----
From: Douglass, Woodrow [mailto:wdouglass@...] 
Sent: Tuesday, 2 June 2009 2:54 AM
To: mspgcc-users@...
Subject: [Mspgcc-users] internal error: out of range error

My program compiles fine, but when I try to link it together, I get this
error:

c:\mspgcc\bin\..\lib\gcc-lib\msp430\3.2.3\libgcc.a(__jump_to_main.o): In
function `__jump_to_main':
(.init9+0x2): undefined reference to `main'
make[1]: *** [main.elf] Error 1
make: *** [newmodule] Error 2

I'm invoking the compiler this way:

msp430-gcc -mmcu=msp430xG4618 -Wl,-Map=./main.map,--cref  --output
main.elf newmodule.o   libs/libmain.a    libs/libkernel.a
libs/libmail.a libs/libversion.a

the archive libmain.a contains a function with the signature "int
main(void)". Is there something else I need to do to get this to link
properly?

Thanks for any insight you can provide!!!

-Woodrow Douglass

 

------------------------------------------------------------------------
------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals.
Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like
Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@...
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Re: [Mspgcc-users] internal error: out of range error

From: Douglass, Woodrow <wdouglass@fo...> - 2009-06-02 12:57

Thanks a lot, it links now. One question though, is this somewhere in
the documentation that I missed? Should it be added? It seems like this
would be a common mistake...

Thanks again!
-Woodrow



-----Original Message-----
From: Wayne Uroda [mailto:Wayne.Uroda@...] 
Sent: Monday, June 01, 2009 9:03 PM
To: GCC for MSP430 - http://mspgcc.sf.net
Subject: Re: [Mspgcc-users] internal error: out of range error

Hi Woodrow,

The linker will only bring in an object if it contains an undefined
symbol when it is read on the command line (it reads files left to
right).

The Symbol main gets referenced in libgcc.a(__jump_to_main.o). Unless
you specify otherwise, libgcc.a is linked last by the linker. This means
when you asked it to link libs/libmain.a it did nothing because that
wasn't required at the time.

You can change the link order like this:

msp430-gcc -mmcu=msp430xG4618 -Wl,-Map=./main.map,--cref --output
main.elf newmodule.o libs/libkernel.a libs/libmail.a libs/libversion.a
-lgcc libs/libmain.a

The -lgcc just tells the linker to pull in libgcc.a from its library
path. It will then see that `main' is undefined, and so will link it
next when it sees libmain.a.

I did a small experiment here like this:

#### This has an error:
> msp430-gcc -mmcu= msp430xG4618 main.a
..../libgcc.a(_reset_vector__.o): In function `_reset_vector__':
config/msp430/libgcc.S:(.init+0x38): undefined reference to `main'

#### But this builds fine:
> msp430-gcc -mmcu= msp430xG4618 -lgcc main.a

I am not a guru on this but I think it should work. I am sure if it
doesn't somebody else here will know the answer.

- Wayne

-----Original Message-----
From: Douglass, Woodrow [mailto:wdouglass@...] 
Sent: Tuesday, 2 June 2009 2:54 AM
To: mspgcc-users@...
Subject: [Mspgcc-users] internal error: out of range error

My program compiles fine, but when I try to link it together, I get this
error:

c:\mspgcc\bin\..\lib\gcc-lib\msp430\3.2.3\libgcc.a(__jump_to_main.o): In
function `__jump_to_main':
(.init9+0x2): undefined reference to `main'
make[1]: *** [main.elf] Error 1
make: *** [newmodule] Error 2

I'm invoking the compiler this way:

msp430-gcc -mmcu=msp430xG4618 -Wl,-Map=./main.map,--cref  --output
main.elf newmodule.o   libs/libmain.a    libs/libkernel.a
libs/libmail.a libs/libversion.a

the archive libmain.a contains a function with the signature "int
main(void)". Is there something else I need to do to get this to link
properly?

Thanks for any insight you can provide!!!

-Woodrow Douglass

 

------------------------------------------------------------------------
------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals.
Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like
Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@...
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the
latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@...
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Re: [Mspgcc-users] internal error: out of range error

From: Wayne Uroda <wayne.uroda@gr...> - 2009-06-02 13:16

It is a GCC linker thing, not just mspgcc. I don't remember how I learned this, probably by asking just like you did.

The only official mention of it I can find is here:

http://gcc.gnu.org/onlinedocs/gcc-3.3.6/gcc/Link-Options.html#Link-Options


It is a very brief mention though. I am unclear myself what happens when library A needs library B - does it then not matter what order they appear in? I am guessing so.


- Wayne
Sent via BlackBerry® from Vodafone

-----Original Message-----
From: "Douglass, Woodrow" <wdouglass@...>

Date: Tue, 2 Jun 2009 08:35:21 
To: GCC for MSP430 - http://mspgcc.sf.net<mspgcc-users@...>>
Subject: Re: [Mspgcc-users] internal error: out of range error


Thanks a lot, it links now. One question though, is this somewhere in
the documentation that I missed? Should it be added? It seems like this
would be a common mistake...

Thanks again!
-Woodrow



-----Original Message-----
From: Wayne Uroda [mailto:Wayne.Uroda@...]
Sent: Monday, June 01, 2009 9:03 PM
To: GCC for MSP430 - http://mspgcc.sf.net
Subject: Re: [Mspgcc-users] internal error: out of range error

Hi Woodrow,

The linker will only bring in an object if it contains an undefined
symbol when it is read on the command line (it reads files left to
right).

The Symbol main gets referenced in libgcc.a(__jump_to_main.o). Unless
you specify otherwise, libgcc.a is linked last by the linker. This means
when you asked it to link libs/libmain.a it did nothing because that
wasn't required at the time.

You can change the link order like this:

msp430-gcc -mmcu=msp430xG4618 -Wl,-Map=./main.map,--cref --output
main.elf newmodule.o libs/libkernel.a libs/libmail.a libs/libversion.a
-lgcc libs/libmain.a

The -lgcc just tells the linker to pull in libgcc.a from its library
path. It will then see that `main' is undefined, and so will link it
next when it sees libmain.a.

I did a small experiment here like this:

#### This has an error:
> msp430-gcc -mmcu= msp430xG4618 main.a
..../libgcc.a(_reset_vector__.o): In function `_reset_vector__':
config/msp430/libgcc.S:(.init+0x38): undefined reference to `main'

#### But this builds fine:
> msp430-gcc -mmcu= msp430xG4618 -lgcc main.a

I am not a guru on this but I think it should work. I am sure if it
doesn't somebody else here will know the answer.

- Wayne

-----Original Message-----
From: Douglass, Woodrow [mailto:wdouglass@...]
Sent: Tuesday, 2 June 2009 2:54 AM
To: mspgcc-users@...
Subject: [Mspgcc-users] internal error: out of range error

My program compiles fine, but when I try to link it together, I get this
error:

c:\mspgcc\bin\..\lib\gcc-lib\msp430\3.2.3\libgcc.a(__jump_to_main.o): In
function `__jump_to_main':
(.init9+0x2): undefined reference to `main'
make[1]: *** [main.elf] Error 1
make: *** [newmodule] Error 2

I'm invoking the compiler this way:

msp430-gcc -mmcu=msp430xG4618 -Wl,-Map=./main.map,--cref  --output
main.elf newmodule.o   libs/libmain.a    libs/libkernel.a
libs/libmail.a libs/libversion.a

the archive libmain.a contains a function with the signature "int
main(void)". Is there something else I need to do to get this to link
properly?

Thanks for any insight you can provide!!!

-Woodrow Douglass



------------------------------------------------------------------------
------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals.
Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like
Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@...
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the
latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@...
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@...
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Re: [Mspgcc-users] internal error: out of range error

From: Wayne Uroda <wayne.uroda@gr...> - 2009-06-02 13:18

I meant to say "I am unclear myself what happens when library A needs library B and vice-versa". Then I wonder if the order matters?

Anyway good luck with it.

- Wayne
Sent via BlackBerry® from Vodafone

-----Original Message-----
From: "Wayne Uroda" <wayne.uroda@...>

Date: Tue, 2 Jun 2009 13:16:22 
To: GCC for MSP430 - http://mspgcc.sf.net<mspgcc-users@...>>
Subject: Re: [Mspgcc-users] internal error: out of range error


It is a GCC linker thing, not just mspgcc. I don't remember how I learned this, probably by asking just like you did.

The only official mention of it I can find is here:

http://gcc.gnu.org/onlinedocs/gcc-3.3.6/gcc/Link-Options.html#Link-Options


It is a very brief mention though. I am unclear myself what happens when library A needs library B - does it then not matter what order they appear in? I am guessing so.


- Wayne
Sent via BlackBerry® from Vodafone

-----Original Message-----
From: "Douglass, Woodrow" <wdouglass@...>

Date: Tue, 2 Jun 2009 08:35:21 
To: GCC for MSP430 - http://mspgcc.sf.net<mspgcc-users@...>>
Subject: Re: [Mspgcc-users] internal error: out of range error


Thanks a lot, it links now. One question though, is this somewhere in
the documentation that I missed? Should it be added? It seems like this
would be a common mistake...

Thanks again!
-Woodrow



-----Original Message-----
From: Wayne Uroda [mailto:Wayne.Uroda@...]
Sent: Monday, June 01, 2009 9:03 PM
To: GCC for MSP430 - http://mspgcc.sf.net
Subject: Re: [Mspgcc-users] internal error: out of range error

Hi Woodrow,

The linker will only bring in an object if it contains an undefined
symbol when it is read on the command line (it reads files left to
right).

The Symbol main gets referenced in libgcc.a(__jump_to_main.o). Unless
you specify otherwise, libgcc.a is linked last by the linker. This means
when you asked it to link libs/libmain.a it did nothing because that
wasn't required at the time.

You can change the link order like this:

msp430-gcc -mmcu=msp430xG4618 -Wl,-Map=./main.map,--cref --output
main.elf newmodule.o libs/libkernel.a libs/libmail.a libs/libversion.a
-lgcc libs/libmain.a

The -lgcc just tells the linker to pull in libgcc.a from its library
path. It will then see that `main' is undefined, and so will link it
next when it sees libmain.a.

I did a small experiment here like this:

#### This has an error:
> msp430-gcc -mmcu= msp430xG4618 main.a
..../libgcc.a(_reset_vector__.o): In function `_reset_vector__':
config/msp430/libgcc.S:(.init+0x38): undefined reference to `main'

#### But this builds fine:
> msp430-gcc -mmcu= msp430xG4618 -lgcc main.a

I am not a guru on this but I think it should work. I am sure if it
doesn't somebody else here will know the answer.

- Wayne

-----Original Message-----
From: Douglass, Woodrow [mailto:wdouglass@...]
Sent: Tuesday, 2 June 2009 2:54 AM
To: mspgcc-users@...
Subject: [Mspgcc-users] internal error: out of range error

My program compiles fine, but when I try to link it together, I get this
error:

c:\mspgcc\bin\..\lib\gcc-lib\msp430\3.2.3\libgcc.a(__jump_to_main.o): In
function `__jump_to_main':
(.init9+0x2): undefined reference to `main'
make[1]: *** [main.elf] Error 1
make: *** [newmodule] Error 2

I'm invoking the compiler this way:

msp430-gcc -mmcu=msp430xG4618 -Wl,-Map=./main.map,--cref  --output
main.elf newmodule.o   libs/libmain.a    libs/libkernel.a
libs/libmail.a libs/libversion.a

the archive libmain.a contains a function with the signature "int
main(void)". Is there something else I need to do to get this to link
properly?

Thanks for any insight you can provide!!!

-Woodrow Douglass



------------------------------------------------------------------------
------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals.
Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like
Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@...
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the
latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@...
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@...
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Re: [Mspgcc-users] internal error: out of range error

From: Przemek Klosowski <przemek.klosowski@gm...> - 2009-06-04 03:13

On Tue, Jun 2, 2009 at 9:18 AM, Wayne Uroda <wayne.uroda@...> wrote:

> I meant to say "I am unclear myself what happens when library A needs
> library B and vice-versa". Then I wonder if the order matters?

At each point in the link the linker has a list of requested external
symbols. Each library is scanned for those symbols;
if it doesn't provide any, it ends up being ignored. In your case, yes the
order matters, Observe:

cat > bar.c
bar(){foo();}

cat > foo.c
foo(){bar();}

cat >test.c
main(){foo();}

gcc -c foo.c bar.c
ar qcv libfoo.a foo.o
ar qcv libbar.a bar.o

So, we've created two libraries, calling each other. Now, linking the wrong
way doesn't work:

 gcc -o test test.c -L. -lbar -lfoo
./libfoo.a(foo.o): In function `foo':
foo.c:(.text+0x7): undefined reference to `bar'
collect2: ld returned 1 exit status

but the other way works:

gcc -o test test.c -L. -lfoo -lbar

In other words, you must place them so that the first one will contain
symbols requested by previous code (foo() call in main(), defined in
libfoo.a). Linking in modules from libfoo will place a request for symbol
bar()  on the list, so that by the time libbar is scanned, they will be
pulled in too. If you put libbar first though, it'll be ignored, and then
libfoo will satisfy the original reference to foo() but it'll be too late to
get bar() from libbar.

Theoretically, the linker could be doing two passes and remember all symbols
from all libraries, but  the current behavior is faster and actually useful
if you have multiply defined symbols---you can juggle them by this explicit
order
mechanism.

Re: [Mspgcc-users] internal error: out of range error

From: Wayne Uroda <Wayne.Uroda@gr...> - 2009-06-04 03:42

Thanks for that, most interesting.

 

Do you know if the linker applies this behaviour to .c and .o files as
well? Or just files linked using -l ?

 

- Wayne

 

 

From: Przemek Klosowski [mailto:przemek.klosowski@...] 
Sent: Thursday, 4 June 2009 1:14 PM
To: Wayne Uroda; GCC for MSP430 - http://mspgcc.sf.net
Subject: Re: [Mspgcc-users] internal error: out of range error

 

 

On Tue, Jun 2, 2009 at 9:18 AM, Wayne Uroda <wayne.uroda@...>
wrote:

I meant to say "I am unclear myself what happens when library A needs
library B and vice-versa". Then I wonder if the order matters?


At each point in the link the linker has a list of requested external
symbols. Each library is scanned for those symbols;
if it doesn't provide any, it ends up being ignored. In your case, yes
the order matters, Observe:

cat > bar.c 
bar(){foo();}

cat > foo.c
foo(){bar();}

cat >test.c
main(){foo();}

gcc -c foo.c bar.c
ar qcv libfoo.a foo.o
ar qcv libbar.a bar.o

So, we've created two libraries, calling each other. Now, linking the
wrong way doesn't work:

 gcc -o test test.c -L. -lbar -lfoo
./libfoo.a(foo.o): In function `foo':
foo.c:(.text+0x7): undefined reference to `bar'
collect2: ld returned 1 exit status

but the other way works:

gcc -o test test.c -L. -lfoo -lbar

In other words, you must place them so that the first one will contain
symbols requested by previous code (foo() call in main(), defined in
libfoo.a). Linking in modules from libfoo will place a request for
symbol  bar()  on the list, so that by the time libbar is scanned, they
will be pulled in too. If you put libbar first though, it'll be ignored,
and then libfoo will satisfy the original reference to foo() but it'll
be too late to get bar() from libbar. 

Theoretically, the linker could be doing two passes and remember all
symbols from all libraries, but  the current behavior is faster and
actually useful if you have multiply defined symbols---you can juggle
them by this explicit order
mechanism.

Re: [Mspgcc-users] internal error: out of range error

From: Przemek Klosowski <przemek.klosowski@gm...> - 2009-06-04 03:52

On Wed, Jun 3, 2009 at 11:42 PM, Wayne Uroda <Wayne.Uroda@...> wrote:

> Do you know if the linker applies this behaviour to .c and .o files as
> well? Or just files linked using -l


The explicitly mentioned .o files are included in the image unconditionally,
I believe.