public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Michael Ambrus <ambrmi09@gmail.com>
Cc: sid@sourceware.org
Subject: Re: Building SID
Date: Mon, 26 Feb 2007 18:54:00 -0000	[thread overview]
Message-ID: <20070226185359.GC19131@redhat.com> (raw)
In-Reply-To: <81c474d20702251644n352ea169kdf6f9ffcbc591fb7@mail.gmail.com>

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

Hi -

On Mon, Feb 26, 2007 at 01:44:54AM +0100, Michael Ambrus wrote:

> [...] The target tried was i386-hixs-elf (hixs is a layer that
> replaces the syscalls with "hooked" versions - i.e. function
> pointers). I haven't worked with x86 for years, so it might be me
> forgetting something (protected mode stuff?).

OK, you should be able to use --target=i386-elf and not bother with
all the other targets.

Since the i386 model is an import from BOCHS, its integration with the
other facilities (i.e., remote debugging) in sid may not have been
quite right.  Try running sid in a highly verbose mode - with
particular attention to the gdb-interface component.

- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-02-26 18:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25 19:37 Michael Ambrus
2007-02-26  0:21 ` Frank Ch. Eigler
2007-02-26  0:45   ` Michael Ambrus
2007-02-26 18:54     ` Frank Ch. Eigler [this message]
2007-02-26 19:42       ` Michael Ambrus
2007-03-02 14:18       ` Michael Ambrus
2007-03-02 15:58         ` Dave Brolley
2007-03-02 16:31           ` Michael Ambrus
2007-03-02 17:22             ` Frank Ch. Eigler
2007-03-02 18:00               ` Michael Ambrus
2007-03-02 18:11                 ` Frank Ch. Eigler
2007-03-02 18:22                   ` Michael Ambrus
2007-03-02 18:45                     ` Dave Brolley
2007-03-02 20:03                       ` Michael Ambrus
     [not found]                   ` <20070303011808.GC18185@redhat.com>
     [not found]                     ` <81c474d20703030457j3775edd7x78211179d3f6d62e@mail.gmail.com>
     [not found]                       ` <20070303143422.GD18185@redhat.com>
     [not found]                         ` <81c474d20703030639i40a30aa4v6a01be2e4160e4cd@mail.gmail.com>
     [not found]                           ` <20070303144102.GF18185@redhat.com>
     [not found]                             ` <81c474d20703030700k2b8d4b32h9e323f0bb8ce90a7@mail.gmail.com>
     [not found]                               ` <20070303163018.GG18185@redhat.com>
     [not found]                                 ` <81c474d20703050549n3577b589gdeccea3db5f33ae7@mail.gmail.com>
     [not found]                                   ` <20070305173328.GA8990@redhat.com>
2007-03-05 22:09                                     ` Michael Ambrus
2007-03-05 22:50                                       ` Frank Ch. Eigler
2007-03-02 17:12           ` Dave Brolley
2007-02-26 16:26   ` Dave Brolley
2007-02-26 17:51     ` Michael Ambrus
2007-02-26 18:54       ` Dave Brolley
2007-02-26 19:12         ` Michael Ambrus

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=20070226185359.GC19131@redhat.com \
    --to=fche@redhat.com \
    --cc=ambrmi09@gmail.com \
    --cc=sid@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).