C++ Build 32bit binary on 64bit system [on hold]












2















So I have a project that I want to be able to build as a 64bit binary as well as as a 32bit one.

My machine itself is 64bit and the 64bit compile works just fine.



I am using cake to build my project and I used the set_target_properties(clib PROPERTIES COMPILE_FLAGS "-m32" LINK_FLAGS "-m32") to force a 32bit build.



Whenever I try to build this the compiler throws an error, because I am including <iostream> in my main program. At first it complained that it couldn't find <bits/c++config.h> which gets included somewhere inside <iostream>.

I found a couple of things online which led me to install g++-multilib on my system. Now the previous error is gone but instead I am getting the error
/usr/include/linux/errno.h:1:10: fatal error: asm/errno.h: No such file or directory which also has its origins in the #include <iostream>.



I checked where this file is and I found it in /usr/include/x86_64-linux-gnu/asm/errno.h but (as before with the c++config.h the x86_64 folder appears to not be searched in a 32bit build (which kinda makes sense).

I also found it in /usr/include/linux/errno.h which is identical to the precious one, but as you can see it is not in the asm subfolder.

Obviously I could manually move it into that folder but I have the feeling that there is something generally wrong with my setup here.



So what else do I have to setup in order for me being able to compile my code (with a #include <iostream>) as a 32bit executable? Is there something like a 32bit-version of the std-library?



EDIT:

I am using Linux Mint 18.3 with g++ --version of g++ (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0 and cmake v.3.10.2






c++ 32bit







share|improve this question















put on hold as off-topic by Jeff Schaller, Thomas, Mr Shunz, msp9011, Archemar Jan 22 at 8:54


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Thomas, Mr Shunz, msp9011, Archemar

If this question can be reworded to fit the rules in the help center, please edit the question.












  • 1





    This should “just work” with g++-multilib and its dependencies (and obviously it doesn’t, I’m not questioning that). What distribution (including its version) are you using?

    – Stephen Kitt
    Jan 18 at 8:14











  • @StephenKitt I added the information in the question - did I miss something?

    – Raven
    Jan 18 at 8:19











  • Does it work if you build the problematic C++ file manually, without cmake? (This will help determine whether g++ is causing problems, or cmake.)

    – Stephen Kitt
    Jan 18 at 11:02











  • @StephenKitt I just tried compiling it via g++ -m32 main.cpp but it resulted in the same error

    – Raven
    Jan 18 at 12:21











  • Okay nvm- I found the issue

    – Raven
    Jan 18 at 12:23
















2















So I have a project that I want to be able to build as a 64bit binary as well as as a 32bit one.

My machine itself is 64bit and the 64bit compile works just fine.



I am using cake to build my project and I used the set_target_properties(clib PROPERTIES COMPILE_FLAGS "-m32" LINK_FLAGS "-m32") to force a 32bit build.



Whenever I try to build this the compiler throws an error, because I am including <iostream> in my main program. At first it complained that it couldn't find <bits/c++config.h> which gets included somewhere inside <iostream>.

I found a couple of things online which led me to install g++-multilib on my system. Now the previous error is gone but instead I am getting the error
/usr/include/linux/errno.h:1:10: fatal error: asm/errno.h: No such file or directory which also has its origins in the #include <iostream>.



I checked where this file is and I found it in /usr/include/x86_64-linux-gnu/asm/errno.h but (as before with the c++config.h the x86_64 folder appears to not be searched in a 32bit build (which kinda makes sense).

I also found it in /usr/include/linux/errno.h which is identical to the precious one, but as you can see it is not in the asm subfolder.

Obviously I could manually move it into that folder but I have the feeling that there is something generally wrong with my setup here.



So what else do I have to setup in order for me being able to compile my code (with a #include <iostream>) as a 32bit executable? Is there something like a 32bit-version of the std-library?



EDIT:

I am using Linux Mint 18.3 with g++ --version of g++ (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0 and cmake v.3.10.2






c++ 32bit







share|improve this question















put on hold as off-topic by Jeff Schaller, Thomas, Mr Shunz, msp9011, Archemar Jan 22 at 8:54


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Thomas, Mr Shunz, msp9011, Archemar

If this question can be reworded to fit the rules in the help center, please edit the question.












  • 1





    This should “just work” with g++-multilib and its dependencies (and obviously it doesn’t, I’m not questioning that). What distribution (including its version) are you using?

    – Stephen Kitt
    Jan 18 at 8:14











  • @StephenKitt I added the information in the question - did I miss something?

    – Raven
    Jan 18 at 8:19











  • Does it work if you build the problematic C++ file manually, without cmake? (This will help determine whether g++ is causing problems, or cmake.)

    – Stephen Kitt
    Jan 18 at 11:02











  • @StephenKitt I just tried compiling it via g++ -m32 main.cpp but it resulted in the same error

    – Raven
    Jan 18 at 12:21











  • Okay nvm- I found the issue

    – Raven
    Jan 18 at 12:23














2












2








2


1






So I have a project that I want to be able to build as a 64bit binary as well as as a 32bit one.

My machine itself is 64bit and the 64bit compile works just fine.



I am using cake to build my project and I used the set_target_properties(clib PROPERTIES COMPILE_FLAGS "-m32" LINK_FLAGS "-m32") to force a 32bit build.



Whenever I try to build this the compiler throws an error, because I am including <iostream> in my main program. At first it complained that it couldn't find <bits/c++config.h> which gets included somewhere inside <iostream>.

I found a couple of things online which led me to install g++-multilib on my system. Now the previous error is gone but instead I am getting the error
/usr/include/linux/errno.h:1:10: fatal error: asm/errno.h: No such file or directory which also has its origins in the #include <iostream>.



I checked where this file is and I found it in /usr/include/x86_64-linux-gnu/asm/errno.h but (as before with the c++config.h the x86_64 folder appears to not be searched in a 32bit build (which kinda makes sense).

I also found it in /usr/include/linux/errno.h which is identical to the precious one, but as you can see it is not in the asm subfolder.

Obviously I could manually move it into that folder but I have the feeling that there is something generally wrong with my setup here.



So what else do I have to setup in order for me being able to compile my code (with a #include <iostream>) as a 32bit executable? Is there something like a 32bit-version of the std-library?



EDIT:

I am using Linux Mint 18.3 with g++ --version of g++ (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0 and cmake v.3.10.2






c++ 32bit







share|improve this question
















So I have a project that I want to be able to build as a 64bit binary as well as as a 32bit one.

My machine itself is 64bit and the 64bit compile works just fine.



I am using cake to build my project and I used the set_target_properties(clib PROPERTIES COMPILE_FLAGS "-m32" LINK_FLAGS "-m32") to force a 32bit build.



Whenever I try to build this the compiler throws an error, because I am including <iostream> in my main program. At first it complained that it couldn't find <bits/c++config.h> which gets included somewhere inside <iostream>.

I found a couple of things online which led me to install g++-multilib on my system. Now the previous error is gone but instead I am getting the error
/usr/include/linux/errno.h:1:10: fatal error: asm/errno.h: No such file or directory which also has its origins in the #include <iostream>.



I checked where this file is and I found it in /usr/include/x86_64-linux-gnu/asm/errno.h but (as before with the c++config.h the x86_64 folder appears to not be searched in a 32bit build (which kinda makes sense).

I also found it in /usr/include/linux/errno.h which is identical to the precious one, but as you can see it is not in the asm subfolder.

Obviously I could manually move it into that folder but I have the feeling that there is something generally wrong with my setup here.



So what else do I have to setup in order for me being able to compile my code (with a #include <iostream>) as a 32bit executable? Is there something like a 32bit-version of the std-library?



EDIT:

I am using Linux Mint 18.3 with g++ --version of g++ (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0 and cmake v.3.10.2






c++ 32bit




c++ 32bit






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 18 at 8:18







Raven

















asked Jan 18 at 8:04









RavenRaven

246115




246115




put on hold as off-topic by Jeff Schaller, Thomas, Mr Shunz, msp9011, Archemar Jan 22 at 8:54


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Thomas, Mr Shunz, msp9011, Archemar

If this question can be reworded to fit the rules in the help center, please edit the question.







put on hold as off-topic by Jeff Schaller, Thomas, Mr Shunz, msp9011, Archemar Jan 22 at 8:54


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Thomas, Mr Shunz, msp9011, Archemar

If this question can be reworded to fit the rules in the help center, please edit the question.








  • 1





    This should “just work” with g++-multilib and its dependencies (and obviously it doesn’t, I’m not questioning that). What distribution (including its version) are you using?

    – Stephen Kitt
    Jan 18 at 8:14











  • @StephenKitt I added the information in the question - did I miss something?

    – Raven
    Jan 18 at 8:19











  • Does it work if you build the problematic C++ file manually, without cmake? (This will help determine whether g++ is causing problems, or cmake.)

    – Stephen Kitt
    Jan 18 at 11:02











  • @StephenKitt I just tried compiling it via g++ -m32 main.cpp but it resulted in the same error

    – Raven
    Jan 18 at 12:21











  • Okay nvm- I found the issue

    – Raven
    Jan 18 at 12:23














  • 1





    This should “just work” with g++-multilib and its dependencies (and obviously it doesn’t, I’m not questioning that). What distribution (including its version) are you using?

    – Stephen Kitt
    Jan 18 at 8:14











  • @StephenKitt I added the information in the question - did I miss something?

    – Raven
    Jan 18 at 8:19











  • Does it work if you build the problematic C++ file manually, without cmake? (This will help determine whether g++ is causing problems, or cmake.)

    – Stephen Kitt
    Jan 18 at 11:02











  • @StephenKitt I just tried compiling it via g++ -m32 main.cpp but it resulted in the same error

    – Raven
    Jan 18 at 12:21











  • Okay nvm- I found the issue

    – Raven
    Jan 18 at 12:23








1




1





This should “just work” with g++-multilib and its dependencies (and obviously it doesn’t, I’m not questioning that). What distribution (including its version) are you using?

– Stephen Kitt
Jan 18 at 8:14





This should “just work” with g++-multilib and its dependencies (and obviously it doesn’t, I’m not questioning that). What distribution (including its version) are you using?

– Stephen Kitt
Jan 18 at 8:14













@StephenKitt I added the information in the question - did I miss something?

– Raven
Jan 18 at 8:19





@StephenKitt I added the information in the question - did I miss something?

– Raven
Jan 18 at 8:19













Does it work if you build the problematic C++ file manually, without cmake? (This will help determine whether g++ is causing problems, or cmake.)

– Stephen Kitt
Jan 18 at 11:02





Does it work if you build the problematic C++ file manually, without cmake? (This will help determine whether g++ is causing problems, or cmake.)

– Stephen Kitt
Jan 18 at 11:02













@StephenKitt I just tried compiling it via g++ -m32 main.cpp but it resulted in the same error

– Raven
Jan 18 at 12:21





@StephenKitt I just tried compiling it via g++ -m32 main.cpp but it resulted in the same error

– Raven
Jan 18 at 12:21













Okay nvm- I found the issue

– Raven
Jan 18 at 12:23





Okay nvm- I found the issue

– Raven
Jan 18 at 12:23










1 Answer
1






active

oldest

votes


















1














Alright I found out what was the problem:

When I found out, I had to use g++-multilib I went ahead and searched for that in my package manager (synaptic in my case). That one listed a bunch of versions so I checked what version of g++ I had installed and then I installed the appropriate g++-multilib-package which in my case was the g++-7-multilib.



However what it didn't install was the gcc-multilib package which appears to be the troublemaker in my case. After having installed that one, it worked as expected.




Long story short: If I had installed the g++-multilib (without a version in the name) package to begin with, I wouldn't have had this problem.






share|improve this answer



















  • 2





    Hah, good one; given your question it would have been difficult to find the answer for you (since you say you installed g++-multilib).

    – Stephen Kitt
    Jan 18 at 12:29











  • Yeah well - I thought I did xD

    – Raven
    Jan 18 at 12:38






  • 1





    Indeed; I’m just glad you found the answer on your own ;-).

    – Stephen Kitt
    Jan 18 at 12:50


















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














Alright I found out what was the problem:

When I found out, I had to use g++-multilib I went ahead and searched for that in my package manager (synaptic in my case). That one listed a bunch of versions so I checked what version of g++ I had installed and then I installed the appropriate g++-multilib-package which in my case was the g++-7-multilib.



However what it didn't install was the gcc-multilib package which appears to be the troublemaker in my case. After having installed that one, it worked as expected.




Long story short: If I had installed the g++-multilib (without a version in the name) package to begin with, I wouldn't have had this problem.






share|improve this answer



















  • 2





    Hah, good one; given your question it would have been difficult to find the answer for you (since you say you installed g++-multilib).

    – Stephen Kitt
    Jan 18 at 12:29











  • Yeah well - I thought I did xD

    – Raven
    Jan 18 at 12:38






  • 1





    Indeed; I’m just glad you found the answer on your own ;-).

    – Stephen Kitt
    Jan 18 at 12:50
















1














Alright I found out what was the problem:

When I found out, I had to use g++-multilib I went ahead and searched for that in my package manager (synaptic in my case). That one listed a bunch of versions so I checked what version of g++ I had installed and then I installed the appropriate g++-multilib-package which in my case was the g++-7-multilib.



However what it didn't install was the gcc-multilib package which appears to be the troublemaker in my case. After having installed that one, it worked as expected.




Long story short: If I had installed the g++-multilib (without a version in the name) package to begin with, I wouldn't have had this problem.






share|improve this answer



















  • 2





    Hah, good one; given your question it would have been difficult to find the answer for you (since you say you installed g++-multilib).

    – Stephen Kitt
    Jan 18 at 12:29











  • Yeah well - I thought I did xD

    – Raven
    Jan 18 at 12:38






  • 1





    Indeed; I’m just glad you found the answer on your own ;-).

    – Stephen Kitt
    Jan 18 at 12:50














1












1








1







Alright I found out what was the problem:

When I found out, I had to use g++-multilib I went ahead and searched for that in my package manager (synaptic in my case). That one listed a bunch of versions so I checked what version of g++ I had installed and then I installed the appropriate g++-multilib-package which in my case was the g++-7-multilib.



However what it didn't install was the gcc-multilib package which appears to be the troublemaker in my case. After having installed that one, it worked as expected.




Long story short: If I had installed the g++-multilib (without a version in the name) package to begin with, I wouldn't have had this problem.






share|improve this answer













Alright I found out what was the problem:

When I found out, I had to use g++-multilib I went ahead and searched for that in my package manager (synaptic in my case). That one listed a bunch of versions so I checked what version of g++ I had installed and then I installed the appropriate g++-multilib-package which in my case was the g++-7-multilib.



However what it didn't install was the gcc-multilib package which appears to be the troublemaker in my case. After having installed that one, it worked as expected.




Long story short: If I had installed the g++-multilib (without a version in the name) package to begin with, I wouldn't have had this problem.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 18 at 12:27









RavenRaven

246115




246115








  • 2





    Hah, good one; given your question it would have been difficult to find the answer for you (since you say you installed g++-multilib).

    – Stephen Kitt
    Jan 18 at 12:29











  • Yeah well - I thought I did xD

    – Raven
    Jan 18 at 12:38






  • 1





    Indeed; I’m just glad you found the answer on your own ;-).

    – Stephen Kitt
    Jan 18 at 12:50














  • 2





    Hah, good one; given your question it would have been difficult to find the answer for you (since you say you installed g++-multilib).

    – Stephen Kitt
    Jan 18 at 12:29











  • Yeah well - I thought I did xD

    – Raven
    Jan 18 at 12:38






  • 1





    Indeed; I’m just glad you found the answer on your own ;-).

    – Stephen Kitt
    Jan 18 at 12:50








2




2





Hah, good one; given your question it would have been difficult to find the answer for you (since you say you installed g++-multilib).

– Stephen Kitt
Jan 18 at 12:29





Hah, good one; given your question it would have been difficult to find the answer for you (since you say you installed g++-multilib).

– Stephen Kitt
Jan 18 at 12:29













Yeah well - I thought I did xD

– Raven
Jan 18 at 12:38





Yeah well - I thought I did xD

– Raven
Jan 18 at 12:38




1




1





Indeed; I’m just glad you found the answer on your own ;-).

– Stephen Kitt
Jan 18 at 12:50





Indeed; I’m just glad you found the answer on your own ;-).

– Stephen Kitt
Jan 18 at 12:50



-

Popular posts from this blog

How to make a Squid Proxy server?

Image
1 I want to set up squid proxy server for monitoring user activity in a network and Internet Web URL filtering for user. I also want to configure the user login, user log, user access group, and block unwanted web sites in my network. Please help me and guide me the full process to do this. server proxy squid share | improve this question edited Jul 31 '12 at 14:45 Jorge Castro 37.1k 107 422 617 asked Jul 31 '12 at 5:16 Goivind Tiwari Goivind Tiwari ...
Read more

Is this a new Fibonacci Identity?

Image
6 1 $begingroup$ I have found the following Fibonacci Identity (and proved it). If $F_n$ denotes the nth Fibonacci Number, we have the following identity begin{equation} F_{n-r+h}F_{n+k+g+1} - F_{n-r+g}F_{n+k+h+1} = (-1)^{n+r+h+1} F_{g-h}F_{k+r+1} end{equation} where $F_1 = F_2 = 1$ , $r leq n$ , $h leq g$ , and $n, g, k in mathbb{N}$ . It is not too hard to show that this identity subsumes Cassini's Identity, Catalan's Identity, Vajda's Idenity, and d'Ocagne's identity to name a few. I have done a pretty thorough literature review, and I have not found anything like this, but I am still wondering if anyone has seen this identity before? I found this by accident after noticing some patterns in some analysis work I was doing, so if this is already known I would be curious to see w...
Read more

19世紀

Image
この記事は検証可能な参考文献や出典が全く示されていないか、不十分です。 出典を追加して記事の信頼性向上にご協力ください。 （ 2012年3月 ） 千年紀: 2千年紀 世紀: 18世紀 - 19世紀 - 20世紀 十年紀: 1800年代 1810年代 1820年代 1830年代 1840年代 1850年代 1860年代 1870年代 1880年代 1890年代 19世紀に君臨した大英帝国。 19世紀 （じゅうきゅうせいき）は、西暦1801年から西暦1900年までの100年間を指す世紀。 目次 1 19世紀の歴史 1.1 国民国家の成立 1.2 帝国主義の興隆 1.3 列強の植民地争奪戦 2 できごと 2.1 1800年代 2.2 1810年代 2.3 1820年代 2.4 1830年代 2.5 1840年代 2.6 1850年代 2.7 1860年代 2.8 1870年代 2.9 1880年代 2.10 1890年代 2.11 1900年代 3 文化 3.1 文学 3.2 音楽 3.3 思想 3.4 科学 3.5 技術 4 人物 4.1 ヨーロッパ 4.1.1 政治家・王族 4.1.1.1 フランス 4.1.1.2 オーストリア＝ハンガリー 4.1.1.3 ロシア 4.1.1.4 イギリス 4.1.1.5 ドイツ（プロイセンほかドイツ領邦を含む） 4.1.1.6 北欧 4.1.1.7 イタリア 4.1.1.8 スペイン 4.1.1.9 ベルギー 4.1.1.10 ギリシア 4.1.2 軍人 4.1.3 実業家 4.1.4 科学と技術 4.1.5 思想と哲学・人文諸学 4.1.6 宗教 4.1.7 文学 4.1.8 美術 4.1.9 音楽 4.1.10 社会事業家 4.1.11 探検家・旅行家 4.1.12 料...
Read more