From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] xterm: force detection of libICE
Date: Sun, 26 Jul 2015 18:13:46 +0200 [thread overview]
Message-ID: <20150726161346.GE3770@free.fr> (raw)
In-Reply-To: <alpine.LNX.2.20.1507261839280.883@bas>
Mikhail, All,
[Please, do not top-post]
On 2015-07-26 18:49 +0300, kyak spake thusly:
> Sure, i should've attached this information in the first place. After all, i
> too used it for debugging of this problem.
>
> Full build log: http://paste.pound-python.org/show/dQ2gfhqx7aQMHAQlRVfK/
>
> config.log: http://paste.pound-python.org/show/EsWJPVSwSaYKN2S0UYJH/
>
> Basically, when configure tests for libICE, it attempts to use host search
> path looking for IceConnectionNumber symbol:
>
> "warning: library search path "/usr/lib64" is unsafe for cross-compilation"
Ah, but then that's what we must fix, instead of forcing detectin of
libICE. So, I'm marking your patch as "Changes Requested" in Patchwork.
Unfortunately, I can't reproduce that leakage on my setup... :-(
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-07-26 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 14:54 [Buildroot] [PATCH 1/1] xterm: force detection of libICE kyak
2015-07-25 21:28 ` Yann E. MORIN
2015-07-26 7:55 ` kyak
2015-07-26 13:32 ` Yann E. MORIN
2015-07-26 15:49 ` kyak
2015-07-26 16:13 ` Yann E. MORIN [this message]
2015-07-26 17:14 ` Romain Naour
2015-07-26 17:47 ` kyak
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=20150726161346.GE3770@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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