From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Titus von Boxberg <titus@v9g.de>, Guylhem Aznar <crossgcc@guylhem.net>
Subject: Re: gdb problem
Date: Thu, 18 Aug 2011 22:00:00 -0000 [thread overview]
Message-ID: <201108190000.23756.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <3838F5CA-B4DE-44C8-9BA2-3EBEA35BAD7E@v9g.de>
Titus, Guylhem, All,
On Wednesday 17 August 2011 23:31:36 Titus von Boxberg wrote:
> Am 17.08.2011 um 22:41 schrieb Guylhem Aznar:
> > -static -L../lib -lncurses -L../lib -lncurses -dynamic -o tic
> -static is not supported on Darwin.
>
> Yann, I thought that static linking was disabled now?
Well, It seems that -static is somehow hard-coded in ncurses-5.7.
In ./configure we can see starting at line 16481:
if test "$GCC" = yes ; then
case $cf_cv_system_name in #(
OS/2*|os2*|aix[45]*) #( vi
LDFLAGS_STATIC=
LDFLAGS_SHARED=
;;
*) #( normally, except when broken
LDFLAGS_STATIC=-static
LDFLAGS_SHARED=-dynamic
;;
esac
else
[--SNIP--]
Here, GCC is set to yes because we are using GNU gcc, and $cf_cv_system_name
is neither OS/2 nor AIX, so we end up in the default case. LDFLAGS_STATIC is
not set later, so it is set to "-static"
Then, in progs/Makefile.in, line 112 (all on one line, split here for
readability:
LIBS_TIC = @LDFLAGS_STATIC@ @TICS_ARGS@ @TINFO_ARGS@ \
@LDFLAGS_SHARED@ @LD_MODEL@ @LIBS@
So we see that both LDFLAGS_STATIC *and* LDFLAGS_SHARED are passed when
linking 'tic'. Bummer... :-(
I just looked at ncurses-5.9, and it's the same... :-/
Titus, did you never encountered the issue on your side?
Well, I'll see if it is sane to pass that through sed to remove -static...
Not tonight, though... So, "on your mark" to beat me to it! ;-)
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
next prev parent reply other threads:[~2011-08-18 22:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 20:42 Guylhem Aznar
2011-08-17 21:31 ` Titus von Boxberg
2011-08-17 21:57 ` Yann E. MORIN
2011-08-18 22:00 ` Yann E. MORIN [this message]
2011-08-19 2:13 ` Guylhem Aznar
2011-08-19 17:41 ` Yann E. MORIN
[not found] ` <201108190032.26721.yann.morin.1998@anciens.enib.fr>
2011-08-19 7:09 ` Titus von Boxberg
2011-08-19 18:59 ` Guylhem Aznar
2011-08-21 15:49 ` compiling ltrace on macos / was " Titus von Boxberg
2011-08-21 18:12 ` Guylhem Aznar
2011-08-22 7:30 ` Titus von Boxberg
2011-08-19 19:00 ` Guylhem Aznar
[not found] ` <201108192000.13342.yann.morin.1998@anciens.enib.fr>
2011-08-19 20:56 ` Titus von Boxberg
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=201108190000.23756.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@guylhem.net \
--cc=crossgcc@sourceware.org \
--cc=titus@v9g.de \
/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).