public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Warhurst Brandon <Warhurst_Brandon@bah.com>
Cc: sid@sources.redhat.com
Subject: Re: SID Faq-O-Matic
Date: Tue, 15 Apr 2003 23:58:00 -0000	[thread overview]
Message-ID: <20030415235758.GA3880@redhat.com> (raw)
In-Reply-To: <3E9C87E5.6D8FBBD7@bah.com>

Hi -


On Tue, Apr 15, 2003 at 06:29:57PM -0400, Warhurst Brandon wrote:
> Okay, everything seems to be in place.  I executed your arm-elf-sid command
> and it generated a nice config-file for me (--no-run so I could look at it
> first).  

Excellent - that's a the ideal start.


> However,
> It is trying to load things from library files and the symbols are
> unresolved.  I must have done something wrong at compile time or something to
> create that problem (dlopen can't seem to resolve anything... don't know
> why).  Do I need to run ldd or something like that to refresh my library
> cache?

If you ran "make install", and run sid out of the configure-time-specified
$prefix/bin directory, it should all just work.  There are a ways to work
around problems anyway.  You can set LD_LIBRARY_PATH to $prefix/lib by
hand.  You could configure sid's build tree with "--disable-shared", so no
shared libraries are built or used.


> Secondly, I created two memory sections, but three show up in the config
> file.  And the third one overlaps the first two.  Is that section generated
> for a reason, or can I safely comment it out?

That's exactly the minor complication I was referring to earlier.  The
perl-based front-end doesn't have an option to omit the default memory
region provided for plain process emulation mode.  Until such an option
appears, yes indeed, commenting the unwanted region is the right thing.
(The minimal change may be just to comment out the "connect-bus" directive
that maps the ram/rom component into the address space.)


- FChE

      parent reply	other threads:[~2003-04-15 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E9ABBE3.6E3A8755@bah.com>
2003-04-14 14:15 ` Frank Ch. Eigler
     [not found]   ` <3E9C2C69.792AB080@bah.com>
     [not found]     ` <20030415121223.D6817@redhat.com>
     [not found]       ` <3E9C87E5.6D8FBBD7@bah.com>
2003-04-15 23:58         ` Frank Ch. Eigler [this message]

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=20030415235758.GA3880@redhat.com \
    --to=fche@redhat.com \
    --cc=Warhurst_Brandon@bah.com \
    --cc=sid@sources.redhat.com \
    /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).