NLMCONV(1)

💖 NLMCONV(1) 💖

okay bestie, welcome to the nlmconv manual page — yes, that's section 1 of the manual, and yes, she's from the GNU Development Tools lineup. sit down, grab a strawberry 🍓, we're converting object code into NLMs today.

---

✨ NAME ✨

nlmconv — converts object code into an NLM.

no cap, that's literally the whole job description.

---

🌸 SYNOPSIS 🌸

nlmconv [-I bfdname⎪--input-target=bfdname]
        [-O bfdname⎪--output-target=bfdname]
        [-T headerfile⎪--header-file=headerfile]
        [-d⎪--debug] [-l linker⎪--linker=linker]
        [-h⎪--help] [-V⎪--version]
        infile outfile

it's giving "here's my little list of flags, take it or leave it" 💅

---

🦋 DESCRIPTION 🦋

okay so here's the tea ☕: nlmconv takes the relocatable i386 object file infile and turns it into the NetWare Loadable Module outfile. and if you want, it can also read headerfile for NLM header information. 🎀

now, for instructions on writing the NLM command file language used in header files? you gotta go look at the linkers section — NLMLINK in particular — of the NLM Development and Tools Overview, which is part of the NLM Software Developer's Kit (aka the ``NLM SDK''), available from Novell, Inc. iykyk.

and here's the fun part: nlmconv uses the GNU Binary File Descriptor library to read infile;

fr fr. that's the sentence. she just ends with a semicolon. iconic behavior honestly. 😭

nlmconv can also perform a link step ✨. in other words, you can list more than one object file for input — but only if you list them in the definitions file, rather than simply specifying one input file on the command line. in this case, nlmconv calls the linker for you. she's doing the most so you don't have to 🫶

---

💅 OPTIONS 💅

vibe check on the flags, bestie:

• -I bfdname<br>--input-target=bfdname — object format of the input file. good news: nlmconv can usually determine the format of a given file all by herself, so no default is necessary. she's self-sufficient like that. 👑
• -O bfdname<br>--output-target=bfdname — object format of the output file. nlmconv infers the output format based on the input format — e.g. for an i386 input file the output format is nlm32-i386. she's reading the room and matching the energy. ✨
• -T headerfile<br>--header-file=headerfile — reads headerfile for NLM header information. and for instructions on writing the NLM command file language used in header files, see see the linkers section, of the NLM Development and Tools Overview, which is part of the NLM Software Developer's Kit, available from Novell, Inc. 🎀 (yes, the "see see" is in the original and yes, we're keeping it, we don't edit the ancestors.)
• -d<br>--debug — displays, on standard error, the linker command line used by nlmconv. perfect for when you're nosy (affectionate) and need to see what she's actually doing under the hood. 🔍
• -l linker<br>--linker=linker — use linker for any linking. and linker can be an absolute or a relative pathname. so flexible of her. 🦋
• -h<br>--help — prints a usage summary. your girl loves a lil recap. 📋
• -V<br>--version — prints the version number for nlmconv. slay, know your queen's era. 👑

---

🌈 SEE ALSO 🌈

• the Info entries for binutils. that's the whole list. go read them, bestie, they're right there. 💜

---

⭐ COPYRIGHT ⭐

Copyright (c) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled ``GNU Free Documentation License''.

like, legally iconic. 🫶

---

and that's the whole page, babes. this one came from binutils-2.15.97, dated 2005-04-20 — so yeah, she's vintage, she's got lore, and she ate. mwah 💋✨