From: Jesper Skov <jskov@cygnus.co.uk>
To: guinan@bluebutton.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] linux .rel.got problem
Date: Tue, 29 Jun 1999 00:26:00 -0000 [thread overview]
Message-ID: <14200.29996.689594.106703@lassi.cygnus.co.uk> (raw)
In-Reply-To: <Pine.LNX.3.96.990629014415.16864C-100000@newt.home.net>
>>>>> "Jamie" == Jamie Guinan <guinan@bluebutton.com> writes:
Jamie> On 21 Jun 1999, Jesper Skov wrote:
>> >>>>> "Jesper" == Jesper Skov <jskov@cygnus.co.uk> writes:
Jesper> Below's the patch used to fix the PR:
>> Which in turn introduces a problem for the ConfigTool.
>>
>> If you use the ConfigTool, you need to change the name of "rel_got"
>> section (in all the files) to "rel__got".
Jamie> Does that apply to running pkgconf.tcl manually as well? (Linux
Jamie> host).
No. As long as the naming is consistent it should be OK on Linux.
Jamie> And a more general question: after applying your patches, is it
Jamie> then necessary to run pkgconf.tcl to generate a new
Jamie> <build>/install/lib/target.ld ?
There's a dependency on the i386/arch script so it should be picked up
automatically. But you need to either rerun pkgconf or copy the new
mlt_i386_linux_ram.ldi to your build tree by hand.
Jesper
next prev parent reply other threads:[~1999-06-29 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-21 5:53 Andrew Lunn
1999-06-21 6:10 ` Jesper Skov
1999-06-21 7:11 ` Jesper Skov
1999-06-28 22:48 ` Jamie Guinan
1999-06-29 0:26 ` Jesper Skov [this message]
1999-06-28 13:07 ` Jamie Guinan
1999-06-28 14:00 ` Jonathan Larmour
1999-06-30 10:49 ` [ECOS] Linux Filesystem Access Jamie Guinan
1999-06-30 11:55 ` [ECOS] " Jamie Guinan
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=14200.29996.689594.106703@lassi.cygnus.co.uk \
--to=jskov@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=guinan@bluebutton.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).