Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to build esp-sdk #418

Open
Kunalverma1502 opened this issue Apr 2, 2021 · 8 comments
Open

Failed to build esp-sdk #418

Kunalverma1502 opened this issue Apr 2, 2021 · 8 comments

Comments

@Kunalverma1502
Copy link

Kunalverma1502 commented Apr 2, 2021

Earlier it was working completely fine.

now whenever I build esp-sdk using

'docker build . -f esp-sdk-dockerfile -t esp-sdk'

It says

[INFO ] Retrieving needed toolchain components' tarballs
[ERROR]
[ERROR] >>
[ERROR] >> Build failed in step 'Retrieving needed toolchain components' tarballs'
[ERROR] >> called in step '(top-level)'
[ERROR] >>
[ERROR] >> Error happened in: do_expat_get[scripts/build/companion_libs/210-expat.sh@12]
[ERROR] >> called from: do_companion_libs_get[scripts/build/companion_libs.sh@15]
[ERROR] >> called from: main[scripts/crosstool-NG.sh@591]
[ERROR] >>
[ERROR] >> For more info on this error, look at the file: 'build.log'
[ERROR] >> There is a list of known issues, some with workarounds, in:
[ERROR] >> 'share/doc/crosstool-ng/crosstool-ng-1.22.0-60-g37b07f6f/B - Known issues.txt'
[ERROR]
[ERROR] (elapsed: 0:55.27)
[00:55] / make[2]: *** [build] Error 1
#9 75.34 ct-ng:152: recipe for target 'build' failed
#9 75.34 make[2]: Leaving directory '/build/esp-open-sdk/crosstool-NG'
#9 75.34 ../Makefile:135: recipe for target '_toolchain' failed
#9 75.34 make[1]: Leaving directory '/build/esp-open-sdk/crosstool-NG'
#9 75.34 make[1]: *** [_toolchain] Error 2
#9 75.34 Makefile:130: recipe for target 'crosstool-NG/.built' failed
#9 75.34 make: *** [crosstool-NG/.built] Error 2

executor failed running [/bin/sh -c su docker -c " git clone --recursive https://github.com/pfalcon/esp-open-sdk.git /build/esp-open-sdk ; cd /build/esp-open-sdk ; make STANDALONE=n ; "]: exit code: 2

@maximkulkin

@ds5apm
Copy link

ds5apm commented Apr 2, 2021

I recently had the same problem on Ubuntu.
Problem search resulted the build stopped because expat-2.2.10.tar.xz could not be downloaded. I downloaded it manually and the build was successful, but
Docker seems to be able to borrow a container that has already been created.

pfalcon/esp-open-sdk#237

@Kunalverma1502
Copy link
Author

can you mention the steps to do the same !
@ds5apm

@ds5apm
Copy link

ds5apm commented Apr 4, 2021

As detailed in the link above, I don't think there is a need to explain further.
As a beginner, the sequence I followed is as follows.
(Details can be found in /esp-open-sdk/crosstool-NG/build.log on your computer.)

  1. Download the file from the address below.
    https://master.dl.sourceforge.net/project/expat/expat/2.2.10/expat-2.2.10.tar.xz

  2. Download "expat-2.1.0.tar.gz"
    Go to ~/esp-open-sdk/crosstool-NG/.build/tarballs folder.

  3. Then rebuild " ...STANDALONE=n"

    I hope my experience will help you solve the problem.

@purofy
Copy link

purofy commented Apr 12, 2021

btw the toolchain is looking for expat-2.1.0.tar.gzfile. The url above is targeting to version 2.2.10.

@nikomaxi
Copy link

nikomaxi commented May 6, 2021

@maximkulkin
Any idea how to solve this while using docker?
get the same errors. but I can't manually edit or download because the image will not be created on error.

Thanks.

@camielverdult
Copy link

It's missing libexpat, adding the following between git clone ... and make STANDALONE=n in esp-sdk-dockerfile fixed it for me:

    cd /build/esp-open-sdk/crosstool-NG ; \
    ls ; \
    mkdir .build ; \
    cd .build ; \
    mkdir tarballs ; \
    cd tarballs ; \
    wget https://github.com/libexpat/libexpat/releases/download/R_2_1_0/expat-2.1.0.tar.gz ; \

@camielverdult
Copy link

The same steps would work if you were to do this manually on a linux VM/machine

@AchimPieters
Copy link

@camielverdult Yup, that works look here for more information.

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

No branches or pull requests

6 participants