Boost C++ Libraries: Ticket #10442: Boost Context library fails for MIPS architecture

attachment set

Vincent.Riera@… — Tue, 02 Sep 2014 13:00:17 GMT

attachment → boost-0001-fix-mips.patch

boost-0001-fix-mips.patch

Vincent.Riera@… — Tue, 02 Sep 2014 13:01:58 GMT

The attached patch fixes the problem. I know is not correct to apply it upstream, but it will help you to identify faster where is the problem.

olli — Tue, 02 Sep 2014 17:23:25 GMT

sorry - the patch is invalid.

could you post the output of b2 ... --debug-building

Vincent.Riera@… — Wed, 03 Sep 2014 09:13:21 GMT

Replying to olli:

sorry - the patch is invalid.

I know the patch is invalid. The only purpose of that patch is to help you to identify the problem faster, as I said in my previous comment.

could you post the output of b2 ... --debug-building

I'm sorry, b2?

attachment set

Vincent.Riera@… — Wed, 03 Sep 2014 09:35:27 GMT

attachment → b2.log

b2 --debug-building log

Vincent.Riera@… — Wed, 03 Sep 2014 09:37:12 GMT

I have attached a file with the output of this command:

./b2 -j1 -d+2 --user-config=/br/output/build/boost-1.56.0/user-config.jam toolset=gcc threading=multi variant=release link=shared runtime-link=shared --prefix=/br/output/host/usr/mips-buildroot-linux-gnu/sysroot/usr --layout=system install --debug-building

Is that what you need?

olli — Wed, 03 Sep 2014 10:05:14 GMT

in the log output I can read: <abi>sysv

it's the wrong property for MIPS (only o32 is valid)

seams that you try a cross-compile try abi=o32 on bjam/b2 command-line

Vincent.Riera@… — Wed, 03 Sep 2014 10:49:30 GMT

Yes, I'm cross-compiling for MIPS32 architecture, so the ABI is o32. From your comment I understand that the boost build system is using the host's ABI instead of the target's one.

If I pass the "abi=o32" option as you suggested, it works. But the thing is that the build system should be smart enough to detect when I'm cross compiling and using the target's ABI instead of the host's ABI.

That problem doesn't happen on other architectures. I have tried cross-compiling for powerpc and arm, and both of them worked fine.

olli — Wed, 03 Sep 2014 11:56:58 GMT

Replying to Vincent.Riera@…:

If I pass the "abi=o32" option as you suggested, it works. But the thing is that the build system should be smart enough to detect when I'm cross compiling and using the target's ABI instead of the host's ABI.

this isn't trivial - I suspect that you can detect at runtime for which ABI your are compiling (you can have multiple like on MIPS)

That problem doesn't happen on other architectures. I have tried cross-compiling for powerpc and arm, and both of them worked fine.

because the default is SYSV

status changed; resolution set

olli — Wed, 03 Sep 2014 11:57:08 GMT

status new → closed
resolution → invalid

anonymous — Wed, 03 Sep 2014 12:10:06 GMT

Replying to olli:

Replying to Vincent.Riera@…:

That problem doesn't happen on other architectures. I have tried cross-compiling for powerpc and arm, and both of them worked fine.

because the default is SYSV

So, you mean that the sysv ABI is valid for powerpc and arm, but not form MIPS?

olli — Wed, 03 Sep 2014 16:55:50 GMT

Replying to anonymous:

Replying to olli:

Replying to Vincent.Riera@…:

That problem doesn't happen on other architectures. I have tried cross-compiling for powerpc and arm, and both of them worked fine.

because the default is SYSV

So, you mean that the sysv ABI is valid for powerpc and arm, but not form MIPS?

no, SYSV ABI is used for x86/non-Windows, powerpc on LINUX etc. ARM uses AAPCS and MIPS O32/N32/N64 etc.