Building SID under Linux - HELP - !

Building SID under Linux - HELP - !

[Stefano Gallina]

Hello all,

I tryed to build Sid under cygwin but i didn't get it
because there are some errors in the source code.
I tryed to build it under Linux and i got the
following error.
Well, is anybody able to build Sid without getting
error messages ?
My aim is simulate a serial port to test some assembly
code written for ARM processor.
I have been advised to use SID with Ecos.
Is there any way to get this aim of mine without using
Sid ?
Using Ecos ?
I noticed that Ecos comes with some examples and one
of them is called serial.c or something like that.
Any idea to fix my problem out?

Cheers.

            Stefano

The error i got is:

rm -fr .libs/libtclapi.la .libs/libtclapi.*
.libs/libtclapi.*
gcc -shared  compTcl.lo  -L/home/src/build/tcl/unix
-ltcl8.3 -L/home/src/build/tk/unix -ltk8.3
-L/usr/X11R6/lib -lSM -lICE -lX11 -ldl -lm -lc 
-Wl,-soname -Wl,libtclapi.so.0 -o
.libs/libtclapi.so.0.0.0
/usr/bin/ld: cannot find -ltk8.3
collect2: ld returned 1 exit status
make[4]: *** [libtclapi.la] Error 1
make[4]: Leaving directory
`/home/src/build/sid/component/tcl'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/src/build/sid/component'
make[2]: *** [all-recursive-am] Error 2
make[2]: Leaving directory
`/home/src/build/sid/component'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/src/build/sid'
make: *** [all-sid] Error 2


=====
First they ignore you
   Then they laugh at you
      Then they fight you
         Then you win

            Mahatma Gandhi

______________________________________________________________________
Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino
http://it.yahoo.com/mail_it/foot/?http://it.mobile.yahoo.com/index2002.html

Re: Building SID under Linux - HELP - !

[Frank Ch. Eigler]

Hi -


> [...]
> Well, is anybody able to build Sid without getting
> error messages ?

Sure, generally.


> My aim is simulate a serial port to test some assembly
> code written for ARM processor.
> I have been advised to use SID with Ecos.
> Is there any way to get this aim of mine without using
> Sid ?  Using Ecos ?

SID is by no means the only way of doing this, but once
you get the system built and familiarized with, it's decent.


> [...]
> The error i got is:
> gcc -shared  compTcl.lo  -L/home/src/build/tcl/unix
> -ltcl8.3 -L/home/src/build/tk/unix -ltk8.3
> -L/usr/X11R6/lib -lSM -lICE -lX11 -ldl -lm -lc 
> [...]
> /usr/bin/ld: cannot find -ltk8.3

It looks like tcl/tk was updated to version 8.4 in the
sourceware repository, but a bit of sid configury wasn't
changed along with it.  That's not normally a problem since
the sid configury backs down to plain -ltk / -ltcl, and
should find OS-supplied libraries.  I wonder why it doesn't
do this in your case.

You could try applying the following patch to sources
within sid/component/tcl, then try to configure/build again.

- FChE


Index: configure
===================================================================
RCS file: /cvs/cvsfiles/devo/sid/component/tcl/configure,v
retrieving revision 1.32
diff -r1.32 configure
2266c2266
<      with_tcl_lib="-L../../../tcl/$tcl_hostdir -ltcl8${tcl_libdot}3"
---
>      with_tcl_lib="-L../../../tcl/$tcl_hostdir -ltcl8${tcl_libdot}4"
2277c2277
<     with_tk_lib="-L../../../tk/$tcl_hostdir -ltk8${tcl_libdot}3"
---
>     with_tk_lib="-L../../../tk/$tcl_hostdir -ltk8${tcl_libdot}4"
3632,3634c3632,3634
<    echo $ac_n "checking for Tcl_Init in -ltcl8${tcl_libdot}3""... $ac_c" 1>&6
< echo "configure:3634: checking for Tcl_Init in -ltcl8${tcl_libdot}3" >&5
< ac_lib_var=`echo tcl8${tcl_libdot}3'_'Tcl_Init | sed 'y%./+-%__p_%'`
---
>    echo $ac_n "checking for Tcl_Init in -ltcl8${tcl_libdot}4""... $ac_c" 1>&6
> echo "configure:3634: checking for Tcl_Init in -ltcl8${tcl_libdot}4" >&5
> ac_lib_var=`echo tcl8${tcl_libdot}4'_'Tcl_Init | sed 'y%./+-%__p_%'`
3639c3639
< LIBS="-ltcl8${tcl_libdot}3  $LIBS"
---
> LIBS="-ltcl8${tcl_libdot}4  $LIBS"
3670c3670
<     ac_tr_lib=HAVE_LIB`echo tcl8${tcl_libdot}3 | sed -e 's/[^a-zA-Z0-9_]/_/g' \
---
>     ac_tr_lib=HAVE_LIB`echo tcl8${tcl_libdot}4 | sed -e 's/[^a-zA-Z0-9_]/_/g' \
3676c3676
<   LIBS="-ltcl8${tcl_libdot}3 $LIBS"
---
>   LIBS="-ltcl8${tcl_libdot}4 $LIBS"
3735,3737c3735,3737
<    echo $ac_n "checking for Tk_Init in -ltk8${tcl_libdot}3""... $ac_c" 1>&6
< echo "configure:3737: checking for Tk_Init in -ltk8${tcl_libdot}3" >&5
< ac_lib_var=`echo tk8${tcl_libdot}3'_'Tk_Init | sed 'y%./+-%__p_%'`
---
>    echo $ac_n "checking for Tk_Init in -ltk8${tcl_libdot}4""... $ac_c" 1>&6
> echo "configure:3737: checking for Tk_Init in -ltk8${tcl_libdot}4" >&5
> ac_lib_var=`echo tk8${tcl_libdot}4'_'Tk_Init | sed 'y%./+-%__p_%'`
3742c3742
< LIBS="-ltk8${tcl_libdot}3  $LIBS"
---
> LIBS="-ltk8${tcl_libdot}4  $LIBS"
3773c3773
<     ac_tr_lib=HAVE_LIB`echo tk8${tcl_libdot}3 | sed -e 's/[^a-zA-Z0-9_]/_/g' \
---
>     ac_tr_lib=HAVE_LIB`echo tk8${tcl_libdot}4 | sed -e 's/[^a-zA-Z0-9_]/_/g' \
3779c3779
<   LIBS="-ltk8${tcl_libdot}3 $LIBS"
---
>   LIBS="-ltk8${tcl_libdot}4 $LIBS"
Index: configure.in
===================================================================
RCS file: /cvs/cvsfiles/devo/sid/component/tcl/configure.in,v
retrieving revision 1.24
diff -r1.24 configure.in
43c43
<      with_tcl_lib="-L../../../tcl/$tcl_hostdir -ltcl8${tcl_libdot}3"
---
>      with_tcl_lib="-L../../../tcl/$tcl_hostdir -ltcl8${tcl_libdot}4"
53c53
<     with_tk_lib="-L../../../tk/$tcl_hostdir -ltk8${tcl_libdot}3"
---
>     with_tk_lib="-L../../../tk/$tcl_hostdir -ltk8${tcl_libdot}4"
103c103
<    AC_CHECK_LIB(tcl8${tcl_libdot}3, Tcl_Init,[],[
---
>    AC_CHECK_LIB(tcl8${tcl_libdot}4, Tcl_Init,[],[
107c107
<    AC_CHECK_LIB(tk8${tcl_libdot}3, Tk_Init,[],[
---
>    AC_CHECK_LIB(tk8${tcl_libdot}4, Tk_Init,[],[

Re: Building SID under Linux - HELP - !

[Ben Elliston]

>>>>> "FChE" == Frank Ch Eigler <fche@redhat.com> writes:

  FChE> You could try applying the following patch to sources
  FChE> within sid/component/tcl, then try to configure/build again.

Frank, you might as well commit this patch.

Ben

Another problem building SID under Linux ! HELP !

[Stefano Gallina]

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

Hello,

here we are , i got another kind of error (take a look
at the text file with the mail) and i feel very bad
because it seems so hard build Sid and i am loosing
the hope to get it.
Any suggestion ? would it possible to have the built
version of Sid instead of speding hours and hours
waiting   in front of the computer ? Could the Red Hat
do this for all the users ? 
Thanks anyway.

=====
First they ignore you
   Then they laugh at you
      Then they fight you
         Then you win

            Mahatma Gandhi

______________________________________________________________________
Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino
http://it.yahoo.com/mail_it/foot/?http://it.mobile.yahoo.com/index2002.html

[-- Attachment #2: SID Error.txt --]
[-- Type: text/plain, Size: 7215 bytes --]

Making all in dynamic
make[3]: Entering directory `/home/src/build/sid/main/dynamic'
c++ -DHAVE_CONFIG_H -I. -I../../../../sid/main/dynamic -I. -I. -I../../include -I../../../../sid/main/dynamic/../../include -I../../../../sid/main/dynamic/../../../include    -g -O2 -c ../../../../sid/main/dynamic/baseCfg.cxx
../../../../sid/main/dynamic/baseCfg.cxx:142: default argument given for
   parameter 5 of `void ComponentCfg::conn_pin(ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   ComponentCfg*, std::basic_string<char, std::char_traits<char>,
   std::allocator<char> >, direction = src_to_dst, bool = true)'
../../../../sid/main/dynamic/baseCfg.h:72: after previous specification in `
   void ComponentCfg::conn_pin(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   direction = src_to_dst, bool = true)'
../../../../sid/main/dynamic/baseCfg.cxx:142: default argument given for
   parameter 6 of `void ComponentCfg::conn_pin(ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   ComponentCfg*, std::basic_string<char, std::char_traits<char>,
   std::allocator<char> >, direction = src_to_dst, bool = true)'
../../../../sid/main/dynamic/baseCfg.h:72: after previous specification in `
   void ComponentCfg::conn_pin(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   direction = src_to_dst, bool = true)'
../../../../sid/main/dynamic/baseCfg.cxx:151: default argument given for
   parameter 5 of `void ComponentCfg::conn_bus(ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   ComponentCfg*, std::basic_string<char, std::char_traits<char>,
   std::allocator<char> >, bool = true)'
../../../../sid/main/dynamic/baseCfg.h:77: after previous specification in `
   void ComponentCfg::conn_bus(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool
   = true)'
../../../../sid/main/dynamic/baseCfg.cxx:159: default argument given for
   parameter 4 of `void ComponentCfg::set(ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool
   = true)'
../../../../sid/main/dynamic/baseCfg.h:81: after previous specification in `
   void ComponentCfg::set(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, bool = true)'
../../../../sid/main/dynamic/baseCfg.cxx:167: default argument given for
   parameter 4 of `void ComponentCfg::relate(ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   ComponentCfg*, bool = true)'
../../../../sid/main/dynamic/baseCfg.h:85: after previous specification in `
   void ComponentCfg::relate(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, ComponentCfg*, bool = true)'
../../../../sid/main/dynamic/baseCfg.cxx:381: default argument given for
   parameter 7 of `Connection::Connection(ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   ComponentCfg*, std::basic_string<char, std::char_traits<char>,
   std::allocator<char> >, bool = true)'
../../../../sid/main/dynamic/baseCfg.h:133: after previous specification in `
   Connection::Connection(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool
   = true)'
../../../../sid/main/dynamic/baseCfg.cxx:394: default argument given for
   parameter 7 of `PinConnection::PinConnection(ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   ComponentCfg*, std::basic_string<char, std::char_traits<char>,
   std::allocator<char> >, direction = src_to_dst, bool = true)'
../../../../sid/main/dynamic/baseCfg.h:151: after previous specification in `
   PinConnection::PinConnection(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   direction = src_to_dst, bool = true)'
../../../../sid/main/dynamic/baseCfg.cxx:394: default argument given for
   parameter 8 of `PinConnection::PinConnection(ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   ComponentCfg*, std::basic_string<char, std::char_traits<char>,
   std::allocator<char> >, direction = src_to_dst, bool = true)'
../../../../sid/main/dynamic/baseCfg.h:151: after previous specification in `
   PinConnection::PinConnection(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   direction = src_to_dst, bool = true)'
../../../../sid/main/dynamic/baseCfg.cxx:460: default argument given for
   parameter 7 of `BusConnection::BusConnection(ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >,
   ComponentCfg*, std::basic_string<char, std::char_traits<char>,
   std::allocator<char> >, bool = true)'
../../../../sid/main/dynamic/baseCfg.h:163: after previous specification in `
   BusConnection::BusConnection(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, ComponentCfg*,
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool
   = true)'
../../../../sid/main/dynamic/baseCfg.cxx:487: default argument given for
   parameter 6 of `Setting::Setting(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, bool = true)'
../../../../sid/main/dynamic/baseCfg.h:190: after previous specification in `
   Setting::Setting(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, bool = true)'
../../../../sid/main/dynamic/baseCfg.cxx:513: default argument given for
   parameter 6 of `Relation::Relation(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, ComponentCfg*, bool = true)'
../../../../sid/main/dynamic/baseCfg.h:174: after previous specification in `
   Relation::Relation(ComponentCfg*, std::basic_string<char,
   std::char_traits<char>, std::allocator<char> >, ComponentCfg*, bool = true)'
make[3]: *** [baseCfg.o] Error 1
make[3]: Leaving directory `/home/src/build/sid/main/dynamic'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/src/build/sid/main'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/src/build/sid'
make: *** [all-sid] Error 2

Re: Another problem building SID under Linux ! HELP !

[Gary Thomas]

On Wed, 2003-01-29 at 11:42, Stefano Gallina wrote:
> Hello,
> 
> here we are , i got another kind of error (take a look
> at the text file with the mail) and i feel very bad
> because it seems so hard build Sid and i am loosing
> the hope to get it.
> Any suggestion ? would it possible to have the built
> version of Sid instead of speding hours and hours
> waiting   in front of the computer ? Could the Red Hat
> do this for all the users ? 
> Thanks anyway.
> 

I can't duplicate this problem.  I've tried building on
Red Hat 7.3 (GCC-2.96) and 8.0 (GCC 3.2).

What host platform (version, etc) are you running on?

-- 
------------------------------------------------------------
Gary Thomas                 |
MLB Associates              |  Consulting for the
+1 (970) 229-1963           |    Embedded world
http://www.mlbassoc.com/    |
email: <gary@mlbassoc.com>  |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------

Re: Another problem building SID under Linux ! HELP !

[Frank Ch. Eigler]

[-- Attachment #1: Type: text/plain, Size: 472 bytes --]

Hi -

On Wed, Jan 29, 2003 at 03:25:51PM -0700, Gary Thomas wrote:
> [...]
> I can't duplicate this problem.  I've tried building on
> Red Hat 7.3 (GCC-2.96) and 8.0 (GCC 3.2). [...]

An even newer compiler traps the standards violation in question.
Briefly, all the function *definitions* in sid/main/dynamic that
include a default value for their arguments should have that
default clause taken away.  (Only function *declarations* should
have default values.)


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Does SID initialize all its components ?

[Stefano Gallina]

hello,

I wrote some assembly programs to comunicate with the
UART1 and UART2 serial ports of SID.
I was surprised that i didn't need to initialize
serial port before send the data to it.
Is it right that SID doesn't need any initialization
of its components before using them?
I noticed that in other assembly programs for ARM
board are used to initializing the serial ports before
sending some data to them.
This feature of SID is great but it can't to
understand how a serial port has to be
initialized....i wrote simple assembly programs for a
course at university.
Cheers.

                   Stefano


Cheers.

                    Stefano


=====
First they ignore you
   Then they laugh at you
      Then they fight you
         Then you win

            Mahatma Gandhi

______________________________________________________________________
Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino
http://it.yahoo.com/mail_it/foot/?http://it.mobile.yahoo.com/index2002.html

Re: Does SID initialize all its components ?

[Frank Ch. Eigler]

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

Hi -


> I wrote some assembly programs to comunicate with the
> UART1 and UART2 serial ports of SID.
> I was surprised that i didn't need to initialize
> serial port before send the data to it.

What kind of initialization did you expect?  I believe
most SID components aim to start up in a state similar
to powerup of the physical devices.  However, since some
features of the hardware may not be emulated, and others
may be hidden by properties of the host I/O, you may get
away with using initial state on the simulator.

This is true in general with simulators: it is possible
to get a "false positive" in the sense that a program
may run on the sim but not on hardware.


> Is it right that SID doesn't need any initialization
> of its components before using them?

Not really.  What you're seeing is probably a coincidence.


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]