public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: scas <scas@itu.dk>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: configtool for linux building problems.
Date: Thu, 11 Jul 2013 13:32:00 -0000	[thread overview]
Message-ID: <1373549565345-238273.post@n7.nabble.com> (raw)
In-Reply-To: <51DEAAEA.1080806@dallaway.org.uk>

Hi John,

Yes I am using the latest makefile. Here's how it looks -
http://pastebin.com/Yzfw2KTF

I feel like this is a linking problem... I've seen that others had problems
with this kind of "i386-linux-gnu/libX11.so so try 
> adding it to the linker command line ", but couldn't understand exactly
> the reason or how to fix it. And unfortunately I am not a Linux guru.
I am trying now to make it compile on Windows but it takes ages, it is so
slow. 

By any change, do you have any other ideas?

Thank you a lot for your time.

Best,
Stefan



--
View this message in context: http://sourceware-org.1504.n7.nabble.com/configtool-for-linux-building-problems-tp196394p238273.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.

-- 
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:[~2013-07-11 13:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4FE4C8BC.80600@dallaway.org.uk>
2012-06-22 19:42 ` John Dallaway
2013-07-11 10:24   ` scas
2013-07-11 12:54     ` John Dallaway
2013-07-11 13:32       ` scas [this message]
2013-07-13 19:28         ` scas
2012-06-20 16:21 [ECOS] " David Fernandez
2012-06-20 19:59 ` [ECOS] " David Fernandez
2012-06-21 22:57   ` David Fernandez
2012-06-22  7:54     ` John Dallaway
2012-06-22 18:26       ` David Fernandez
2012-06-22  9:18     ` Alex Schuilenburg

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=1373549565345-238273.post@n7.nabble.com \
    --to=scas@itu.dk \
    --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).