[SOLVED] Slackware standard configure script options?
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It seems I need to recompile binutils for some stoopid option in objcopy. It's being compiled on Slackware64-14.0, for slackware64-14.0. I'd need to get efi object compatibility on objcopy. So from the top source, does this look OK?
Specifies the subsystem under which your program will execute. The
legal values for which are "native", "windows", "console", "posix",
"efi-app", "efi-bsd", "efi-rtd", "sal-rtd", and "xbox". You may
optionally set the subsystem version also. Numeric values are also
accepted for which. [This option is specific to PE targets.]
and this :-o.
Using GNU toolchain for compiling and debugging EFI applications
GNU development toolchain consist of binutils package (assembler, linker, various utilities for manipulating executable images), GCC compiler, GNU make and GDB debugger. Advantages are obvious - build system is very flexible, the tools have very rich functionality, they are free and open source, your EFI application code can be easily integrated to any project. Most of open source software prefers this way.
The first step is to compile your tools with required options. Firstly you need to compile binutils package. Obtain the latest from http://ftp.gnu.org/gnu/binutils/. You will need to enable "i386-efi-pe" target to have support for EFI PE+ executable format. If you use the same toolchain for compiling something else in your project (e.g. OS kernel) you can also specify required target (e.g. x86_64-myOS-freebsd) Note that it is BFD target, not the target platform. If you want to develop for 64-bits platform add "--enable-64-bit-bfd" options to "configure" script.
These targets don't show in ./configure --help, and there's talk 5 years back of this stuff, so I presume they exist. So I tried all those options to see what it would throw out. It threw out build, host & target but pointed out (wrongly) that most of the tools had been just compiled :-/.
First, you'll want to use the same options used when compiling the standard package (plus your options), so refer to the official SlackBuild for those. Then, find out about the efi options available with `./configure --help` or by searching the configure.ac or configure.in file for 'efi'. Then edit the SlackBuild to add the options you need and use it to create the package.
Checking the Slackbuild in Slackware it seems to already be setup.
One bit of it is. When I built it straight with my own options and none of the other stuff, last night, I had no problems and it swallowed everything. Building from the slackbuild, it's complaining about the --enable-targets line and keeps barfing because of the silly things. At least I have the original options, which is good. I'll postpone this until I'm sure objcopy barfs.
On another note, I needed to rebuild the kernel to add in the 'relocatable' option. This whole UEFI thing is a @£#@%! nightmare, because everyone does it differently. It can be disabled, and you can use a 'legacy OS' But how to set up a bootloader for the legacy os is the best kept secret out there.
Last edited by business_kid; 12-10-2012 at 11:41 AM.
To develop x86 and x86_64 EFI applications, the following tools are needed:
. . . . .
- A version of "objcopy" that supports EFI applications. To
check if your version includes EFI support, issue the
and verify that the line "supported targets" contains the
string "efi-app-ia32" and "efi-app-x86_64". The binutils release
binutils-18.104.22.168.14 supports Intel64 EFI.
- For debugging purposes, it's useful to have a version of
"objdump" that supports EFI applications as well. This
allows inspect and disassemble EFI binaries.
Slackware's does not. And we need a relocatable kernel.