public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Guylhem Aznar <crossgcc@guylhem.net>
To: Titus von Boxberg <titus@v9g.de>
Cc: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>,
	crossgcc@sourceware.org
Subject: Re: gdb problem
Date: Fri, 19 Aug 2011 19:00:00 -0000	[thread overview]
Message-ID: <CAAVXy570_-3CEo=hoRqeVkBJ4+zC8-62NVyNr7ub+tPG80Do2w@mail.gmail.com> (raw)
In-Reply-To: <ED31CCCA-E67F-4B4C-AC46-C2B2807CC889@v9g.de>

Hello

On Fri, Aug 19, 2011 at 03:09, Titus von Boxberg <titus@v9g.de> wrote:
> If the former, then why not simply tackle those problems and add a fix?

It might be complicated without a platform to test - the reason why I
offered to put a mac online to try to compile.

> Guylhem, mind to send me again your most current .config.
> I'd give it a try on the weekend.

Here is one which work with the uclibc find fixes, and which I will
release soon. It is incomplete however (see "still getting errors"
message : no gdb/gdbserver, no strace)

Some notes :
 CT_DEBUG_PAUSE_STEPS and CT_DEBUG_CT_SAVE_STEPS have been disabled
because I don't understand how to resume a build - with or without
them, it just fails.
 CT_GDB_V_6_8 has been disabled. It would have been nice to run gdb
and gdbserver on the mips target, but it cause the tic static bug, and
the tree.ref bug to appear
 CT_LTRACE_V_0_5_3 has been disabled due to make not finding a file
called "Darwin"

Maybe you could try to enable one on more of these options to fix the
remaining bugs? (the build resuming thing might not be a bug, just a
misunderstanding on my part)

BTW - would it be possible to use a uclibc 0.9.29 with the current
crosstools-ng release? the target for which I'm preparing a cross
toolchain use this very version. I have had problems with some
binaries compiled for 0.9.30, so at the moment I'm compiling
everything static.

-- 
vCard: http://guylhem.tel

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

  parent reply	other threads:[~2011-08-19 19: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
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 [this message]
     [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='CAAVXy570_-3CEo=hoRqeVkBJ4+zC8-62NVyNr7ub+tPG80Do2w@mail.gmail.com' \
    --to=crossgcc@guylhem.net \
    --cc=crossgcc@sourceware.org \
    --cc=titus@v9g.de \
    --cc=yann.morin.1998@anciens.enib.fr \
    /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).