public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: David Fernandez <dfernandez@cct.co.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Problems building ecos sources
Date: Thu, 23 Feb 2006 11:33:00 -0000	[thread overview]
Message-ID: <1140691695.2885.25.camel@software.cct.co.uk> (raw)
In-Reply-To: <20060222213922.GP19406@lunn.ch>

On Wed, 2006-02-22 at 22:39 +0100, Andrew Lunn wrote:
> On Wed, Feb 22, 2006 at 04:56:09PM +0000, David Fernandez wrote:
> > On Wed, 2006-02-22 at 17:53 +0100, Andrew Lunn wrote:
> > > On Wed, Feb 22, 2006 at 04:49:42PM +0000, David Fernandez wrote:
> > > > 
> > > > 	Hi there,
> > > > 
> > > > 	I'm trying to configure and make the gcc-2.0 tarball, but gives several
> > > > warnings about compiler options not supported for C++, and finally it
> > > > stops complaining about undefined dinamic linker symbols.
> > > > 
> > > > 	I'm using gcc-4.0.2 toolchain, does it support that?
> > > > 
> > > > 	Any ideas about what could be wrong?
> > > 
> > > So you are using gcc-4.0.2 to compile gcc-2.0? Why do you want to use
> > > such an old version of gcc?
> > > 
> > >         Andrew
> > 
> > 	Ooops, I meant ecos-2.0...
> 
> I've not used the old ecos-2.0 for many years....
> 
> I just compiled anonymous cvs using gcc 4.0.3. As you said there are
> lots of warning, but it does compile.
> 
> I suggest you upgrade to annoncvs.
> 
>         Andrew

	I've downloaded this time the file ecos-trunk-full.tar.bz2 from
ecoscentric (I don't have cvs access at work, but it is supposed to be a
weekly snapshot from the CVS, right?), Extract it in /opt, made a
$HOME/ecos-build directory, gone into it, run /opt/ecos/configure
--prefix=/usr/local/ecos, run make. And this is the result:

[root@software ecos-build]# make
...
c++ -pipe -Wall -Wpointer-arith -Wbad-function-cast -Wcast-qual
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs
-Woverloaded-virtual -O0   -o ecosconfig  ecosconfig.o cdl_exec.o
build.o flags.o  -lcdl -lcyginfra -L/usr/local/ecos/lib -ltcl8.4
-L/root/ecos-build/host/libcdl -L/root/ecos-build/host/infra
/usr/local/ecos/lib/libtcl8.4.a(tclLoadDl.o)(.text+0x2a): In function
`TclpDlopen':
/usr/src/redhat/BUILD/insight-6.1/tcl/unix/../unix/tclLoadDl.c:78:
undefined reference to `dlopen'
/usr/local/ecos/lib/libtcl8.4.a(tclLoadDl.o)(.text
+0x7b):/usr/src/redhat/BUILD/insight-6.1/tcl/unix/../unix/tclLoadDl.c:88: undefined reference to `dlopen'
/usr/local/ecos/lib/libtcl8.4.a(tclLoadDl.o)(.text
+0x95):/usr/src/redhat/BUILD/insight-6.1/tcl/unix/../unix/tclLoadDl.c:93: undefined reference to `dlerror'
/usr/local/ecos/lib/libtcl8.4.a(tclLoadDl.o)(.text+0x10a): In function
`TclpFindSymbol':
/usr/src/redhat/BUILD/insight-6.1/tcl/unix/../unix/tclLoadDl.c:136:
undefined reference to `dlsym'
/usr/local/ecos/lib/libtcl8.4.a(tclLoadDl.o)(.text
+0x174):/usr/src/redhat/BUILD/insight-6.1/tcl/unix/../unix/tclLoadDl.c:142: undefined reference to `dlsym'
/usr/local/ecos/lib/libtcl8.4.a(tclLoadDl.o)(.text+0x1bb): In function
`TclpUnloadFile':
/usr/src/redhat/BUILD/insight-6.1/tcl/unix/../unix/tclLoadDl.c:179:
undefined reference to `dlclose'
collect2: ld returned 1 exit status
make[3]: *** [ecosconfig] Error 1
make[3]: Leaving directory
`/root/ecos-build/host/tools/configtool/standalone/common'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/root/ecos-build/host/tools/configtool/standalone/common'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/ecos-build/host'
make: *** [all-recursive] Error 1

	Why? (almost the same as with ecos-2.0 tarball)

David.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2006-02-23 10:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 16:49 David Fernandez
2006-02-22 16:54 ` Andrew Lunn
     [not found]   ` <1140627369.2878.18.camel@software.cct.co.uk>
2006-02-22 21:39     ` Andrew Lunn
2006-02-23 11:33       ` David Fernandez [this message]
2006-02-23 15:02         ` Andrew Lunn
2006-02-23 15:37           ` David Fernandez
2006-02-23 15:51             ` Andrew Lunn
2006-02-23 16:48             ` [ECOS] " John Dallaway
     [not found]               ` <1140716284.2885.45.camel@software.cct.co.uk>
2006-02-24  6:11                 ` Andrew Lunn
2006-02-24 16:38                   ` David Fernandez
2006-02-24 17:14                     ` Andrew Lunn
2006-02-24 22:00                     ` [ECOS] " David Fernandez
2006-02-26  5:19                       ` Andrew Lunn
2006-02-27 10:09                         ` David Fernandez
2006-02-27 11:25                           ` Andrew Lunn
2006-02-27 15:35                             ` David Fernandez
     [not found]                             ` <1141032779.2878.13.camel@software.cct.co.uk>
2006-02-27 18:14                               ` Andrew Lunn
2006-02-27 22:48                                 ` David Fernandez
2006-05-14  2:51                                   ` Frank Pagliughi
2006-02-26 23:13                       ` Chuck McManis
2006-02-27  9:33                         ` David Fernandez
2006-02-23 17:30         ` Andrew Lunn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1140691695.2885.25.camel@software.cct.co.uk \
    --to=dfernandez@cct.co.uk \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).