public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Stefan Hallas Mulvad <shm@hallas.nu>
To: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: GDB build failure from tip
Date: Wed, 27 Jul 2016 18:11:00 -0000	[thread overview]
Message-ID: <F606C8F6-CE80-4F27-9F2B-25CD94A15402@hallas.nu> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C6EE86C987@ex-mb1.corp.adtran.com>

[-- Attachment #1: Type: text/plain, Size: 2109 bytes --]

Hi Andy,

Sorry, should have mentioned that - glad it worked out ;=)

Best regards,
Stefan

> On Jul 27, 2016, at 10:31 AM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
> 
> Stefan,
> 
> Thanks!  That did work (after I saved the file -- you didn't
> tell me I had to make the change AND save the file ;)).
> 
> Andy
> 
>> -----Original Message-----
>> From: crossgcc-owner@sourceware.org [mailto:crossgcc-owner@sourceware.org] On Behalf Of ANDY KENNEDY
>> Sent: Tuesday, July 26, 2016 7:13 PM
>> To: 'Stefan Hallas Mulvad'
>> Cc: crossgcc@sourceware.org
>> Subject: RE: GDB build failure from tip
>> 
>> Stefan,
>> 
>> Looks like I was seriously confused on the below...
>> 
>> So, I guess the below "CROSS_STATIC" means the gdb built
>> for the TARGET to run on HOST. . .
>> 
>> This seems too confusing to me (and backwards).
>> 
>> Anyways, using your patch now and I found that it didn't work.
>> 
>> Thanks!
>> 
>> Andy
>> 
>>> Line 95:
>>>        CC_for_gdb="${CT_HOST}-gcc ${CT_CFLAGS_FOR_HOST} ${CT_LDFLAGS_FOR_HOST}"
>>>        LD_for_gdb="${CT_HOST}-ld ${CT_LDFLAGS_FOR_HOST}"
>>>        if [ "${CT_GDB_CROSS_STATIC}" = "y" ]; then
>>>            CC_for_gdb+=" -static"
>>>            LD_for_gdb+=" -static"
>>>        fi
>>> 
>>> Line 195:
>>>        [ "${CT_TOOLCHAIN_ENABLE_NLS}" != "y" ] &&    \
>>>        native_extra_config+=("--disable-nls")
>>> 
>>>        if [ "${CT_GDB_NATIVE_STATIC}" = "y" ]; then
>>>            CC_for_gdb="${CT_TARGET}-gcc -static"
>>>            LD_for_gdb="${CT_TARGET}-ld -static"
>>>        else
>>>            CC_for_gdb="${CT_TARGET}-gcc"
>>>            LD_for_gdb="${CT_TARGET}-ld"
>>>        fi
>>> 
>>> Thanks for the info, though!
>>> 
>>> Andy
>>> 
>>>> 
>>>> Hope it works,
>>>> 
>>>> Best regards,
>>>> Stefan
>>> 
>>> 
>>> --
>>> For unsubscribe information see http://sourceware.org/lists.html#faq
>> 
>> 
>> --
>> For unsubscribe information see http://sourceware.org/lists.html#faq
> 
> 
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
> 


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]

  reply	other threads:[~2016-07-27 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 22:46 ANDY KENNEDY
2016-07-26 22:57 ` Stefan Hallas Mulvad
2016-07-26 23:04   ` ANDY KENNEDY
2016-07-27  0:13     ` ANDY KENNEDY
2016-07-27 17:32       ` ANDY KENNEDY
2016-07-27 18:11         ` Stefan Hallas Mulvad [this message]
2016-07-27 20:19           ` ANDY KENNEDY

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=F606C8F6-CE80-4F27-9F2B-25CD94A15402@hallas.nu \
    --to=shm@hallas.nu \
    --cc=ANDY.KENNEDY@adtran.com \
    --cc=crossgcc@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).