From: Bernd Herd <herdsoft@t-online.de>
To: binutils@sources.redhat.com, crossgcc@sources.redhat.com
Subject: i386-netware-ld target for Netware NLM files with C++ support
Date: Sat, 19 Apr 2003 17:33:00 -0000 [thread overview]
Message-ID: <3EA18726.509@t-online.de> (raw)
Hello,
I've developed a patch to the i386-netware target to allow creation of
NLMs from C++ sources. The work consists of two parts concerning binutils:
- Extension of the linker scripts for netware
- A shell script to integrate nlmconv into the link process.
The whole project is downloadable and documented at
http://www.herdsoft.com/ti/netware/cross/
NLMs were conventionally created with binutils by combining ld and
nlmconv. ld is used for a -Ur partial link to an ELF target and nlmconv
converts the ELF to the NLM format speciying a lot of options in a
linker definition file.
Since handling this is very uncomfortable, I've integrated nlmconv into
the link process by creating a BASH script "ld" that parses the
parameters passed from gcc, creates temporary control files and runs the
GNU linker "gld" and "nlmconv". That way compilation to the netware
target works exactly as to a unix target:
i386-netware-g++ -o hello.nlm hello.cpp
and
i386-netware-gcc -s -shared -o dll.nlm dll.c
i386-netware-gcc -s -o app.nlm app.c dll.nlm
The appraoch also allows to run configure scripts for the netware target
as long as the configure scripts are prepared for cross-compilation.
Any suggestion on how to integrate the "ld" script approach into the
binutils distribution?
Yours
Bernd Herd
:-)
next reply other threads:[~2003-04-19 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 17:33 Bernd Herd [this message]
2003-04-25 13:26 ` Nick Clifton
2003-05-07 8:57 ` Bernd Herd
2003-05-07 17:10 ` Ian Lance Taylor
[not found] ` <3EB9475E.3070800@herdsoft.com>
[not found] ` <m3u1c6hb1p.fsf@gossamer.airs.com>
2003-05-09 19:25 ` Bernd Herd
2003-05-09 20:03 ` Ian Lance Taylor
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=3EA18726.509@t-online.de \
--to=herdsoft@t-online.de \
--cc=binutils@sources.redhat.com \
--cc=crossgcc@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).