Related articles |
---|
Linking scripts and interpreters into an executable jkahrs@castor.atlas.de (Juergen Kahrs) (1998-07-30) |
Re: Linking scripts and interpreters into an executable rpereda@ringer.cs.utsa.edu (Ray Pereda) (1998-08-10) |
Re: Linking scripts and interpreters into an executable Juergen.Kahrs@t-online.de (1998-08-10) |
Re: Linking scripts and interpreters into an executable bob@netwrench.com (1998-08-13) |
Re: Linking scripts and interpreters into an executable dan@control.com (1998-08-13) |
Re: Linking scripts and interpreters into an executable aeb@saltfarm.bt.co.uk (Tony Bass) (1998-08-16) |
Re: Linking scripts and interpreters into an executable jkahrs@castor.atlas.de (Juergen Kahrs) (1998-08-17) |
From: | Juergen Kahrs <jkahrs@castor.atlas.de> |
Newsgroups: | comp.compilers |
Date: | 30 Jul 1998 23:21:03 -0400 |
Organization: | STN Atlas Elektronik GmbH SLE1 |
Keywords: | interpreter, question, comment |
Hello,
I just read the spec of the Executable and Linking Format (ELF), the
file format that is used on modern operating systems for executables.
The GNU ld linker is able to produce such code, but AFAIK, it does
not have an option for (statically) linking scripts (shell, AWK, Perl)
together with their interpreters into an executable.
Does anyone know of a linker which can do this ?
| Juergen Kahrs, STN Atlas Elektronik GmbH, D-28305 Bremen |
| Simulation Division Sebaldsbruecker Heerstr. 235 +49/421/457-2819 |
+----------- http://home.t-online.de/home/Juergen.Kahrs/ -------------+
[It's not just a linker you need, you'd also need a version of the
language interpreter that was prepared to read from strings in the
program. But it sounds like a rather peculiar thing to do with little
practical benefit. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.