How to install 'build-essential:i386' on Debian 7.9 x64
Clash Royale CLAN TAG#URR8PPP
I'm on Debian 7.9 (wheezy) x64, and I would like to install build-essential: i386
.
I already added i386
in dpkg --architecture
, updated aptitude
and installed java-jdk-1.6:i386
successfully.
BTW, no matter how I try, build-essential
systematically generates an error of dependencies with:
apt-get install build-essential:i386
Depend : dpkg-dev:i386 (>= 1.13.5)
E: Unable to correct problems, you have held broken packages...
If someone has an idea... Thanks.
Also, I found this http://bit.ly/1WFGzYA
"I want to have the build-essential for i386 installed on amd64. I
could install build-essential:i386, replacing gcc/g++:amd64 with
gcc/g++:i386. Wouldn't that give me everything needed to cross-compile
for i386?
In that case, yes, because you can run x86 code on an AMD64 or Intel
64 CPU. Though you would indeed be replacing gcc-4.7:amd64 etc. with
gcc-4.7:i386 etc. as the packages aren't co-installable with
themselves."
Is it true ?
debian compiling x86
add a comment |
I'm on Debian 7.9 (wheezy) x64, and I would like to install build-essential: i386
.
I already added i386
in dpkg --architecture
, updated aptitude
and installed java-jdk-1.6:i386
successfully.
BTW, no matter how I try, build-essential
systematically generates an error of dependencies with:
apt-get install build-essential:i386
Depend : dpkg-dev:i386 (>= 1.13.5)
E: Unable to correct problems, you have held broken packages...
If someone has an idea... Thanks.
Also, I found this http://bit.ly/1WFGzYA
"I want to have the build-essential for i386 installed on amd64. I
could install build-essential:i386, replacing gcc/g++:amd64 with
gcc/g++:i386. Wouldn't that give me everything needed to cross-compile
for i386?
In that case, yes, because you can run x86 code on an AMD64 or Intel
64 CPU. Though you would indeed be replacing gcc-4.7:amd64 etc. with
gcc-4.7:i386 etc. as the packages aren't co-installable with
themselves."
Is it true ?
debian compiling x86
3
Post the commands you are using and your errors, please.
– Faheem Mitha
Feb 22 '16 at 17:59
Put it in the question, not the comments, please. I get a similar error on my system, so I'd guess this is something you are not supposed to do. I'll ask the experts.
– Faheem Mitha
Feb 23 '16 at 8:45
The same question on AU: askubuntu.com/q/510269/15729.
– Faheem Mitha
Feb 23 '16 at 9:04
add a comment |
I'm on Debian 7.9 (wheezy) x64, and I would like to install build-essential: i386
.
I already added i386
in dpkg --architecture
, updated aptitude
and installed java-jdk-1.6:i386
successfully.
BTW, no matter how I try, build-essential
systematically generates an error of dependencies with:
apt-get install build-essential:i386
Depend : dpkg-dev:i386 (>= 1.13.5)
E: Unable to correct problems, you have held broken packages...
If someone has an idea... Thanks.
Also, I found this http://bit.ly/1WFGzYA
"I want to have the build-essential for i386 installed on amd64. I
could install build-essential:i386, replacing gcc/g++:amd64 with
gcc/g++:i386. Wouldn't that give me everything needed to cross-compile
for i386?
In that case, yes, because you can run x86 code on an AMD64 or Intel
64 CPU. Though you would indeed be replacing gcc-4.7:amd64 etc. with
gcc-4.7:i386 etc. as the packages aren't co-installable with
themselves."
Is it true ?
debian compiling x86
I'm on Debian 7.9 (wheezy) x64, and I would like to install build-essential: i386
.
I already added i386
in dpkg --architecture
, updated aptitude
and installed java-jdk-1.6:i386
successfully.
BTW, no matter how I try, build-essential
systematically generates an error of dependencies with:
apt-get install build-essential:i386
Depend : dpkg-dev:i386 (>= 1.13.5)
E: Unable to correct problems, you have held broken packages...
If someone has an idea... Thanks.
Also, I found this http://bit.ly/1WFGzYA
"I want to have the build-essential for i386 installed on amd64. I
could install build-essential:i386, replacing gcc/g++:amd64 with
gcc/g++:i386. Wouldn't that give me everything needed to cross-compile
for i386?
In that case, yes, because you can run x86 code on an AMD64 or Intel
64 CPU. Though you would indeed be replacing gcc-4.7:amd64 etc. with
gcc-4.7:i386 etc. as the packages aren't co-installable with
themselves."
Is it true ?
debian compiling x86
debian compiling x86
edited Feb 23 '16 at 8:59
m4hmud
asked Feb 22 '16 at 17:49
m4hmudm4hmud
65
65
3
Post the commands you are using and your errors, please.
– Faheem Mitha
Feb 22 '16 at 17:59
Put it in the question, not the comments, please. I get a similar error on my system, so I'd guess this is something you are not supposed to do. I'll ask the experts.
– Faheem Mitha
Feb 23 '16 at 8:45
The same question on AU: askubuntu.com/q/510269/15729.
– Faheem Mitha
Feb 23 '16 at 9:04
add a comment |
3
Post the commands you are using and your errors, please.
– Faheem Mitha
Feb 22 '16 at 17:59
Put it in the question, not the comments, please. I get a similar error on my system, so I'd guess this is something you are not supposed to do. I'll ask the experts.
– Faheem Mitha
Feb 23 '16 at 8:45
The same question on AU: askubuntu.com/q/510269/15729.
– Faheem Mitha
Feb 23 '16 at 9:04
3
3
Post the commands you are using and your errors, please.
– Faheem Mitha
Feb 22 '16 at 17:59
Post the commands you are using and your errors, please.
– Faheem Mitha
Feb 22 '16 at 17:59
Put it in the question, not the comments, please. I get a similar error on my system, so I'd guess this is something you are not supposed to do. I'll ask the experts.
– Faheem Mitha
Feb 23 '16 at 8:45
Put it in the question, not the comments, please. I get a similar error on my system, so I'd guess this is something you are not supposed to do. I'll ask the experts.
– Faheem Mitha
Feb 23 '16 at 8:45
The same question on AU: askubuntu.com/q/510269/15729.
– Faheem Mitha
Feb 23 '16 at 9:04
The same question on AU: askubuntu.com/q/510269/15729.
– Faheem Mitha
Feb 23 '16 at 9:04
add a comment |
3 Answers
3
active
oldest
votes
Edit /etc/apt/sources.list
and add the following line:
deb http://ftp.de.debian.org/debian sid main
Update and reinstall build_essential
Also you can run apt-get build-dep $package
and it will install the build dependencies for that package
add a comment |
Well, the thing is, you do not really need build-essential:i386 on a amd64 system, depending on what you want to compile, you might need libpam-dev:i386 or other 32bit -dev libraries, but you should use the 64bit tools, even to generate 32bit code, mainly because they should, in theory, run faster ... they have access to more memory ...
I solved my problem with by installing g++-multilib & gcc-multilib.
– m4hmud
Feb 23 '16 at 14:39
add a comment |
Yes, it's true that you can't have build-essential:i386
and build-essential:amd64
installed at the same time. That would require the presence of two instances of some executables (for example gcc
), and that isn't supported by the Multiarch Specification:
Unresolved issues
Co-installable packages for executables
Co-installation of executables would potentially make it possible to reuse a single disk image on systems of multiple architectures with no modification. This could be implemented on top of multiarch using architecture-qualified paths for executables, but would require an additional mechanism (such as kernel support, or boot-time symlinking) to implement PATH handling.
Can you quote the relevant portion of the "MultiArch Specification" or other relevant document? I took a quick look at the "MultiArch Specification", but don't see the specific point addressed there.
– Faheem Mitha
Feb 23 '16 at 10:58
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f265072%2fhow-to-install-build-essentiali386-on-debian-7-9-x64%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Edit /etc/apt/sources.list
and add the following line:
deb http://ftp.de.debian.org/debian sid main
Update and reinstall build_essential
Also you can run apt-get build-dep $package
and it will install the build dependencies for that package
add a comment |
Edit /etc/apt/sources.list
and add the following line:
deb http://ftp.de.debian.org/debian sid main
Update and reinstall build_essential
Also you can run apt-get build-dep $package
and it will install the build dependencies for that package
add a comment |
Edit /etc/apt/sources.list
and add the following line:
deb http://ftp.de.debian.org/debian sid main
Update and reinstall build_essential
Also you can run apt-get build-dep $package
and it will install the build dependencies for that package
Edit /etc/apt/sources.list
and add the following line:
deb http://ftp.de.debian.org/debian sid main
Update and reinstall build_essential
Also you can run apt-get build-dep $package
and it will install the build dependencies for that package
answered Feb 22 '16 at 20:54
GAD3RGAD3R
26.7k1756110
26.7k1756110
add a comment |
add a comment |
Well, the thing is, you do not really need build-essential:i386 on a amd64 system, depending on what you want to compile, you might need libpam-dev:i386 or other 32bit -dev libraries, but you should use the 64bit tools, even to generate 32bit code, mainly because they should, in theory, run faster ... they have access to more memory ...
I solved my problem with by installing g++-multilib & gcc-multilib.
– m4hmud
Feb 23 '16 at 14:39
add a comment |
Well, the thing is, you do not really need build-essential:i386 on a amd64 system, depending on what you want to compile, you might need libpam-dev:i386 or other 32bit -dev libraries, but you should use the 64bit tools, even to generate 32bit code, mainly because they should, in theory, run faster ... they have access to more memory ...
I solved my problem with by installing g++-multilib & gcc-multilib.
– m4hmud
Feb 23 '16 at 14:39
add a comment |
Well, the thing is, you do not really need build-essential:i386 on a amd64 system, depending on what you want to compile, you might need libpam-dev:i386 or other 32bit -dev libraries, but you should use the 64bit tools, even to generate 32bit code, mainly because they should, in theory, run faster ... they have access to more memory ...
Well, the thing is, you do not really need build-essential:i386 on a amd64 system, depending on what you want to compile, you might need libpam-dev:i386 or other 32bit -dev libraries, but you should use the 64bit tools, even to generate 32bit code, mainly because they should, in theory, run faster ... they have access to more memory ...
answered Feb 23 '16 at 9:48
thecarpythecarpy
2,295825
2,295825
I solved my problem with by installing g++-multilib & gcc-multilib.
– m4hmud
Feb 23 '16 at 14:39
add a comment |
I solved my problem with by installing g++-multilib & gcc-multilib.
– m4hmud
Feb 23 '16 at 14:39
I solved my problem with by installing g++-multilib & gcc-multilib.
– m4hmud
Feb 23 '16 at 14:39
I solved my problem with by installing g++-multilib & gcc-multilib.
– m4hmud
Feb 23 '16 at 14:39
add a comment |
Yes, it's true that you can't have build-essential:i386
and build-essential:amd64
installed at the same time. That would require the presence of two instances of some executables (for example gcc
), and that isn't supported by the Multiarch Specification:
Unresolved issues
Co-installable packages for executables
Co-installation of executables would potentially make it possible to reuse a single disk image on systems of multiple architectures with no modification. This could be implemented on top of multiarch using architecture-qualified paths for executables, but would require an additional mechanism (such as kernel support, or boot-time symlinking) to implement PATH handling.
Can you quote the relevant portion of the "MultiArch Specification" or other relevant document? I took a quick look at the "MultiArch Specification", but don't see the specific point addressed there.
– Faheem Mitha
Feb 23 '16 at 10:58
add a comment |
Yes, it's true that you can't have build-essential:i386
and build-essential:amd64
installed at the same time. That would require the presence of two instances of some executables (for example gcc
), and that isn't supported by the Multiarch Specification:
Unresolved issues
Co-installable packages for executables
Co-installation of executables would potentially make it possible to reuse a single disk image on systems of multiple architectures with no modification. This could be implemented on top of multiarch using architecture-qualified paths for executables, but would require an additional mechanism (such as kernel support, or boot-time symlinking) to implement PATH handling.
Can you quote the relevant portion of the "MultiArch Specification" or other relevant document? I took a quick look at the "MultiArch Specification", but don't see the specific point addressed there.
– Faheem Mitha
Feb 23 '16 at 10:58
add a comment |
Yes, it's true that you can't have build-essential:i386
and build-essential:amd64
installed at the same time. That would require the presence of two instances of some executables (for example gcc
), and that isn't supported by the Multiarch Specification:
Unresolved issues
Co-installable packages for executables
Co-installation of executables would potentially make it possible to reuse a single disk image on systems of multiple architectures with no modification. This could be implemented on top of multiarch using architecture-qualified paths for executables, but would require an additional mechanism (such as kernel support, or boot-time symlinking) to implement PATH handling.
Yes, it's true that you can't have build-essential:i386
and build-essential:amd64
installed at the same time. That would require the presence of two instances of some executables (for example gcc
), and that isn't supported by the Multiarch Specification:
Unresolved issues
Co-installable packages for executables
Co-installation of executables would potentially make it possible to reuse a single disk image on systems of multiple architectures with no modification. This could be implemented on top of multiarch using architecture-qualified paths for executables, but would require an additional mechanism (such as kernel support, or boot-time symlinking) to implement PATH handling.
edited Feb 24 '16 at 10:05
answered Feb 23 '16 at 10:37
Ferenc WágnerFerenc Wágner
2,994920
2,994920
Can you quote the relevant portion of the "MultiArch Specification" or other relevant document? I took a quick look at the "MultiArch Specification", but don't see the specific point addressed there.
– Faheem Mitha
Feb 23 '16 at 10:58
add a comment |
Can you quote the relevant portion of the "MultiArch Specification" or other relevant document? I took a quick look at the "MultiArch Specification", but don't see the specific point addressed there.
– Faheem Mitha
Feb 23 '16 at 10:58
Can you quote the relevant portion of the "MultiArch Specification" or other relevant document? I took a quick look at the "MultiArch Specification", but don't see the specific point addressed there.
– Faheem Mitha
Feb 23 '16 at 10:58
Can you quote the relevant portion of the "MultiArch Specification" or other relevant document? I took a quick look at the "MultiArch Specification", but don't see the specific point addressed there.
– Faheem Mitha
Feb 23 '16 at 10:58
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f265072%2fhow-to-install-build-essentiali386-on-debian-7-9-x64%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
Post the commands you are using and your errors, please.
– Faheem Mitha
Feb 22 '16 at 17:59
Put it in the question, not the comments, please. I get a similar error on my system, so I'd guess this is something you are not supposed to do. I'll ask the experts.
– Faheem Mitha
Feb 23 '16 at 8:45
The same question on AU: askubuntu.com/q/510269/15729.
– Faheem Mitha
Feb 23 '16 at 9:04