public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Trevor Woerner <twoerner@gmail.com>
Subject: Re: ncurses tic
Date: Mon, 15 Mar 2010 21:30:00 -0000	[thread overview]
Message-ID: <201003152230.04518.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <f415e2731003151407w79d4107bxafa4daf584621f85@mail.gmail.com>

Trevor, All,

On Monday 15 March 2010 22:07:00 Trevor Woerner wrote:
> When crosstool configures ncurses tic it does so as follows:
> ==> Executing: '/home/trevor/devel/crosstool/1.6.1/build/x86/targets/src/ncurses-5.7/configure
> --build=x86_64-suse-linux --host=x86_64-build_suse-linux-gnu

In fact, it's doing:
    [...]
    --build=${CT_REAL_BUILD}
    --host=${CT_BUILD}
    [...]

> --prefix=/usr --without-shared --enable-symlinks
> --with-build-cc=x86_64-suse-linux-gcc
> --with-build-cpp=x86_64-suse-linux-gcc --with-build-cflags= -pipe
> --without-ada'

I already have seen some weirdness on the openSuSE machine of a friend of
mine. He was not interested in a native gdb for his target, and I had no
time to investigate. Now is a good time, as someone seems interested in
fixing this! :-)

> But I think it should instead be:
> --with-build-cc=x86_64-build_suse-linux-gnu-gcc
> --with-build-cpp=x86_64-build_suse-linux-gnu-gcc

Not quite sure... build.log, please.

> Am I doing something unexpected?

That sample is just bulding fine for me. I did not want to reproduce the
1.6.0 error, where not all samples were tested, so for 1.6.1 I tested all
samples on my machine (Debian lenny 5.0.4). So if you just recalled that
sample, you did nothing wrong, but there seems to be some issue with how
openSuSe (and SuSE?) configured their tuple... We'll have to fix that,
if you have a little time to investigate. But first, I'd need your
build.log, please.

Regards,
Yann E. MORIN.


-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2010-03-15 21:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 21:07 Trevor Woerner
2010-03-15 21:30 ` Yann E. MORIN [this message]
     [not found]   ` <f415e2731003151844u69efccb7rd737dfcb89491339@mail.gmail.com>
2010-03-16 18:31     ` Yann E. MORIN
2010-03-16 18:46       ` Trevor Woerner
2010-03-16 19:07         ` *** SPAM ***Re: " Yann E. MORIN
     [not found]           ` <4BA381A3.3070704@tx.rr.com>
2010-03-19 14:09             ` Trevor Woerner
2010-03-21  3:43               ` David Dyck
2010-03-19 14:19           ` Harold Grovesteen
2010-03-16 20:28         ` Trevor Woerner
2010-03-16 20:29           ` Trevor Woerner
2010-03-16 22:07           ` Yann E. MORIN
2010-03-17 19:31             ` Trevor Woerner

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=201003152230.04518.yann.morin.1998@anciens.enib.fr \
    --to=yann.morin.1998@anciens.enib.fr \
    --cc=crossgcc@sourceware.org \
    --cc=twoerner@gmail.com \
    /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).