porting Ruby to an embedded target

[Wilde, Donald S]

Greetings, Rubyists -

I am in the midst of porting the Ruby interpreter to our embedded Intel CE =
SoC (as used in GoogleTV and Boxee Box), and I would appreciate some knowle=
dgeable help.

Here is my configure script, with e-variables:

# begin shell script
SDK_ROOT=3D/opt/DHG/target/sdk-perl/IntelCE-21.1.11174.270772; export SDK_R=
OOT

/configure \
--prefix=3D$SDK_ROOT/build_i686/staging_dir \
--exec-prefix=3D$SDK_ROOT/build_i686/staging_dir \
--target=3Di686 \
--enable-shared
CC=3D$SDK_ROOT/build_i686/staging_dir/i686-cm-linux/bin/gcc; export CC
CFLAGS=3D"-O2 -Wall"; export CFLAGS
LDFLAGS=3D$SDK_ROOT/build_i686/i686-linux-elf/lib; export LDFLAGS
CPPFLAGS=3D""
CXX=3D$SDK_ROOT/build_i686/staging_dir/i686-cm-linux/bin/g++; export CXX
# end shell script

Here's the end of the output of make:

ld -o .ext/i686-none/enc/encdb.so enc/encdb.o -L. -L. -L. -Wl,-R -Wl,/o=
pt/DHG/target/sdk-perl/IntelCE-21.1.11174.270772/build_i686/staging_dir/lib=
-L/opt/DHG/target/sdk-perl/IntelCE-21.1.11174.270772/build_i686/staging_di=
r/lib -lruby -lpthread -lrt -ldl -lcrypt -lm =20
ld: unrecognized option '-Wl, -R'

I know I need to find system headers and add a -I; which ones and what else=
is needed?

Thanks in advance!

-- Don Wilde

 

[brabuhr]

I am in the midst of porting the Ruby interpreter to our embedded Intel C=

E SoC (as used in GoogleTV and Boxee Box), and I would appreciate some know=
ledgeable help.

Here's the end of the output of make:

ld -o .ext/i686-none/enc/encdb.so enc/encdb.o -L. -L. -L. =A0 =A0 -Wl,-R =

-Wl,/opt/DHG/target/sdk-perl/IntelCE-21.1.11174.270772/build_i686/staging_d=
ir/lib -L/opt/DHG/target/sdk-perl/IntelCE-21.1.11174.270772/build_i686/stag=
ing_dir/lib -lruby -lpthread -lrt -ldl -lcrypt -lm

ld: unrecognized option '-Wl, -R'

-Wl is an option on GNU ld: "Pass option as an option to the
linker."[1] I don't know if the Intel CE SoC SDK has an equivalent ld
option.

[1] http://gcc.gnu.org/onlinedocs/gcc/Link-Options.html

 

[Wilde, Donald S]

-----Original Message-----
From: (e-mail address removed) [mailto:[email protected]] On Behalf Of=
(e-mail address removed)
Sent: Friday, May 27, 2011 11:52 AM
To: ruby-talk ML
Subject: Re: porting Ruby to an embedded target

On Fri, May 27, 2011 at 1:54 PM, Wilde, Donald S

ld: unrecognized option '-Wl, -R'

-Wl is an option on GNU ld: "Pass option as an option to the
linker."[1] I don't know if the Intel CE SoC SDK has an equivalent ld
option.

[1] http://gcc.gnu.org/onlinedocs/gcc/Link-Options.html

Hmmm... we use GNU tools to compile our SDK. According to that page the cal=
l looks good.

It's GNU ld, version 2.20.20100303. Is it perhaps the space between the com=
ma and the -R option? I know GNU is sometimes less than flexible about that=
It's all from the 4.5.1 gcc package and associated bintools.

 

[brabuhr]

Hmmm... we use GNU tools to compile our SDK. According to that page the call looks good.

It's GNU ld, version 2.20.20100303. Is it perhaps the space between the comma and the -R option? I know GNU is sometimes less than flexible about that. It's all from the 4.5.1 gcc package and associated bintools.

Is there a space? It looks like there was no space in the actual
command but only in the error message.

 

[Wilde, Donald S]

-----Original Message-----
From: Wilde, Donald S=20
Sent: Friday, May 27, 2011 12:34 PM
To: ruby-talk ML
Subject: RE: porting Ruby to an embedded target


-----Original Message-----
From: (e-mail address removed) [mailto:[email protected]] On Behalf Of=
(e-mail address removed)
Sent: Friday, May 27, 2011 11:52 AM
To: ruby-talk ML
Subject: Re: porting Ruby to an embedded target

On Fri, May 27, 2011 at 1:54 PM, Wilde, Donald S

ld: unrecognized option '-Wl, -R'

-Wl is an option on GNU ld: "Pass option as an option to the
linker."[1] I don't know if the Intel CE SoC SDK has an equivalent ld
option.
[1] http://gcc.gnu.org/onlinedocs/gcc/Link-Options.html

Hmmm... we use GNU tools to compile our SDK. According to that page the c=

all looks good.

It's GNU ld, version 2.20.20100303. Is it perhaps the space between the c= omma and=20
the -R option? I know GNU is sometimes less than flexible about that. It'= s all from=20
the 4.5.1 gcc package and associated bintools.

The -Wl,-R is incorrect in that it's looking for a symbol table file after =
the -R.=20
Adding a -g to my CFLAGS didn't help.