From: micro13 <grzegorz.heldt@gmail.com>
To: ecos-devel@ecos.sourceware.org
Subject: Re: problem with building ecos
Date: Wed, 30 Jan 2008 08:22:00 -0000 [thread overview]
Message-ID: <15177206.post@talk.nabble.com> (raw)
In-Reply-To: <20080129075932.GA9045@sg-ubuntu>
Hello Sergei
Thank You very much, I succesfully compile ecos infrastructure and
configtool after more careful reading of README.host.
Cheers
Grzegorz Heldt.
Sergei Gavrikov-4 wrote:
>
> On Mon, Jan 28, 2008 at 11:12:13PM -0800, micro13 wrote:
>>
>> Hello !
>> It??s my first post on this forum, so hello everyone and please, don??t
>> kill
>> me.
>>
>> I have a problem with building latest ecos sources that I get from CVS
>> two
>> days ago.
>>
>> micro@u:~/workspace/ecosbuild$updatedb
>>
>> micro@u:~/workspace/ecosbuild$ locate tclConfig.sh
>> /usr/lib/tcl8.4/tclConfig.sh
>> micro@u:~/workspace/ecosbuild$ ../ecos/configure
>> --prefix=/home/micro/workspace/ecosbuild/ --with-tcl=8.4
> [snip]
>
> cut from README.host
>
> 3) --with-tcl=<path>
> --with-tcl-version=<number>
>
> So, a right configure call is
>
> ./configure --prefix=<yours> --with-tcl-version=8.4
>
> Sergei
>
> P.S.
>
> IMHO, it's better to post the n.b. questions in ecos-discuss list.
>
>> My system is ubuntu under vmware.
>> I??ve tried everything I found on internet.
>> Thanks for any help.
>> --
>> View this message in context:
>> http://www.nabble.com/problem-with-building-ecos-tp15153681p15153681.html
>> Sent from the Sourceware - ecos-devel mailing list archive at Nabble.com.
>
>
--
View this message in context: http://www.nabble.com/problem-with-building-ecos-tp15153681p15177206.html
Sent from the Sourceware - ecos-devel mailing list archive at Nabble.com.
prev parent reply other threads:[~2008-01-30 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 7:12 micro13
2008-01-29 8:00 ` Sergei Gavrikov
2008-01-30 8:22 ` micro13 [this message]
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=15177206.post@talk.nabble.com \
--to=grzegorz.heldt@gmail.com \
--cc=ecos-devel@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).