Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I was browsing the go source and I wanted to build it as a standalone linker for osx that can generate mach-o files. Is there anyway to do this?
The linker is already a standalone tool. You can see it by running
go tool -n 6l
which will print the location of the 6l (x86 64 bit linker) executable.
The source code of 6l can be found in GOROOT/src/cmd/6l.
In that directory you can use make to build it.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am developing an operating system using C, Assembler and the GCC Cross Compiler. I have already implemented a working kernel that prints to the screen and allows the user to type in some simple commands. I have already looked into some file systems such as FAT32 and LFS. What other options do I have about implementing my very own filesystem?
There's always Practical File System Design with the Be File System (PDF).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Basically what I want is to create an object file (maybe x64 ELF one) with assembly code which could then be linked with other object files in order to create one executable. Also I would like to export some addresses from this object and also to import some from the other object files it will link to.
I'll be happy if it can target linux x64 (I'm using OpenSuse now) and can be used with some default linker (like 'ld' maybe).
I want to make a compiler using 'C' language.
Just generate assembly code, and use the assembler to convert to object format.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have Cygwin, but can't figure out how to install GCC, Nano, Emacs or anything of the sort. Any help is appreciated.
You should select the installation of gcc and g++ when installing cygwin.
Here is a screenshot:
Also a quick google search gave me this and this which may also answer your question about nano and emacs
you can use TDM . A compiler suite for 32- and 64-bit Windows based on the GNU toolchain
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
How does otool and similar tools read load commands? I could not find any open source tools to figure this out (even though otool is partially open source). How does it parse the binary file? Where does it start?
Thanks
I would expect that the otool command would open the file and parse the header of the binary according to the OSX ABI Mach-O File Format
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
while reading docs for FreeBSD 7.3 gdb, I saw a mention of built directory info stored in binary files. How is it stored, and how could it be retrieved?
If a binary is built with debug info, then it will contain debug symbol information that contains full path names, so when you debug, your debugger can find source files and correlate source code with execution. Open the binary file in any hex editor and you will be able to see the path strings