Skip to content

Conversation

@arturkow2000
Copy link

libc6-dev-i386 is required to build i386 edk2 code

This package is installed separately because attempt to do this in a single command resulted in failure:

Sending build context to Docker daemon  96.77kB
Step 1/8 : FROM ubuntu:16.04
 ---> b6f507652425
Step 2/8 : MAINTAINER Piotr Król <[email protected]>
 ---> Using cache
 ---> 61822e0b4470
Step 3/8 : RUN 	DEBIAN_FRONTEND=noninteractive apt-get -qq update && 	DEBIAN_FRONTEND=noninteractive apt-get -qqy install 		ccache 		build-essential 		python 		python-pip 		qemu 		sudo 		vim 		libgcc-5-dev 		uuid-dev 		nasm 		iasl 		git 		gcc-aarch64-linux-gnu 		gcc-arm-linux-gnueabihf 		wget 		zip 		libc6-dev-i386 	&& DEBIAN_FRONTEND=noninteractive apt-get clean
 ---> Running in 326ee6686f3a
E: Unable to correct problems, you have held broken packages.
The command '/bin/sh -c DEBIAN_FRONTEND=noninteractive apt-get -qq update && 	DEBIAN_FRONTEND=noninteractive apt-get -qqy install 		ccache 		build-essential 		python 		python-pip 		qemu 		sudo 		vim 		libgcc-5-dev 		uuid-dev 		nasm 		iasl 		git 		gcc-aarch64-linux-gnu 		gcc-arm-linux-gnueabihf 		wget 		zip 		libc6-dev-i386 	&& DEBIAN_FRONTEND=noninteractive apt-get clean' returned a non-zero code: 100

Signed-off-by: Artur Kowalski [email protected]

libc6-dev-i386 is required to build i386 edk2 code

Signed-off-by: Artur Kowalski <[email protected]>
@macpijan macpijan requested a review from miczyg1 October 7, 2022 12:59
gcc-arm-linux-gnueabihf \
wget \
zip \
&& DEBIAN_FRONTEND=noninteractive apt-get -qqy install \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
&& DEBIAN_FRONTEND=noninteractive apt-get -qqy install \

No need to do apt-get install again. SImply add the module to the list.

@krystian-hebel
Copy link
Contributor

Why would firmware depend on system libraries in the first place? Are there any intermediate build tools built as 32b binaries on 64b system? If this is caused by firmware code then there is something wrong with that code, probably wrong or missing header file, and that is what should be fixed, not the Docker image. (Also, please don't put links nor logs in the response to this comment, I'm aware of what lead to this change, but NDA 🤐).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants