combine two GCC compiled .o object files into a third .o file

Question

How does one combine two GCC compiled .o object files into a third .o file?

$ gcc -c  a.c -o a.o
$ gcc -c  b.c -o b.o
$ ??? a.o b.o -o c.o
$ gcc c.o other.o -o executable

If you have access to the source files the -combine GCC flag will merge the source files before compilation:

$ gcc -c -combine a.c b.c -o c.o

However this only works for source files, and GCC does not accept .o files as input for this command.

Normally, linking .o files does not work properly, as you cannot use the output of the linker as input for it. The result is a shared library and is not linked statically into the resulting executable.

$ gcc -shared a.o b.o -o c.o
$ gcc c.o other.o -o executable
$ ./executable
./executable: error while loading shared libraries: c.o: cannot open shared object file: No such file or directory
$ file c.o
c.o: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped
$ file a.o
a.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped

gcc does not currently have a -combine option. It exists in gcc 4.1.2 and does not exist in gcc 6.3.0 (someone else can figure out just when it was removed). — Keith Thompson
– Keith Thompson, Commented Jul 11, 2019 at 23:05

Eric Postpischil · Accepted Answer · 2025-07-21 16:55:55Z

118

Passing --relocatable or -r to ld will create an object that is suitable as input of ld.

$ ld --relocatable a.o b.o -o c.o
$ gcc c.o other.o -o executable
$ ./executable

The generated file is of the same type as the original .o files.

$ file a.o
a.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped
$ file c.o
c.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped

For an in-depth explanation see MaskRay's Relocatable linking article.

edited Jul 21 at 16:55

Eric Postpischil

233k15 gold badges199 silver badges379 bronze badges

answered Jun 5, 2010 at 11:26

Lucian Adrian Grijincu

2,5813 gold badges18 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

Bert Regelink Over a year ago

Is it possible to do the inverse operation? i.e. produce a.o and b.o from c.o?

Alec Teal Over a year ago

@BertRegelink no, because there's no unique inverse, In maths terms, doesn't forma group :P

Martin Bonner supports Monica Over a year ago

Warning: --relocatable seems to be less portable. The ld that comes with Android NDK only recognizes -relocatable. If you need portability, stick to -r.

Martin Bonner supports Monica Over a year ago

@matthijs The word is the same; the difference is one minus or two.

Matthijs Kooijman Over a year ago

Ah, didn't see that. So, the Android NDK only recognizes -relocatable and -r, but not --relocatable. Thanks for clarifying!

|

score 10 · Accepted Answer · 2010-06-05 11:30:18Z

10

If you want to create an archive of two or more .o files (i.e.. a static library) use the ar command:

ar rvs mylib.a file1.o file2.o

edited Jun 5, 2010 at 11:30

answered Jun 5, 2010 at 11:19

anon

1 Comment

Lucian Adrian Grijincu Over a year ago

I need to run objcopy on the resulting file and make some kinds of symbols local to the file so that they are not visible externally. Some of the symbols that need be localized are referenced between the a.o and b.o files. I can't localize individual files – as the symbols would not be found at linker time – and I can't localize symbols from the static archive either.

Collectives™ on Stack Overflow

combine two GCC compiled .o object files into a third .o file

2 Answers 2

7 Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

7 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related