ffmpegwasm / ffmpegwasm/ffmpeg.wasm

Build with docker failed

Abierto
#207 1 comentario 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
C
Estrellas
17.8k
Forks
1.1k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

Hi, I'm building ffmpeg.wasm-core on Ubuntu server with `./build-with-docker.sh`, the error message:

```
cp: 'fribidi-unicode-version.h' and './fribidi-unicode-version.h' are the same file
cp: 'fribidi.h' and './fribidi.h' are the same file
make[3]: *** [Makefile:594: c2man.stamp] Error 1
make[3]: Leaving directory '/src/third_party/fribidi/doc'
make[2]: *** [Makefile:603: fribidi_parse_charset.3] Error 2
make[3]: *** [Makefile:594: c2man.stamp] Error 1
make[3]: Leaving directory '/src/third_party/fribidi/doc'
make[2]: *** [Makefile:603: fribidi_get_par_embedding_levels_ex.3] Error 2
make[3]: *** [Makefile:594: c2man.stamp] Error 1
make[3]: Leaving directory '/src/third_party/fribidi/doc'
make[2]: *** [Makefile:603: fribidi_get_type_internal.3] Error 2
make[3]: stat: fribidi-arabic.h: Too many levels of symbolic links
make[3]: stat: fribidi-begindecls.h: Too many levels of symbolic links
make[3]: stat: fribidi-bidi.h: Too many levels of symbolic links
make[3]: stat: fribidi-bidi-types.h: Too many levels of symbolic links
make[3]: stat: fribidi-bidi-types-list.h: Too many levels of symbolic links
make[3]: stat: fribidi-common.h: Too many levels of symbolic links
make[3]: 'c2man.stamp' is up to date.
make[3]: Leaving directory '/src/third_party/fribidi/doc'
make[2]: Leaving directory '/src/third_party/fribidi/doc'
make[1]: *** [Makefile:501: install-recursive] Error 1
make[1]: Leaving directory '/src/third_party/fribidi'
make: *** [Makefile:809: install] Error 2
make: Leaving directory '/src/third_party/fribidi'
make: make -C third_party/fribidi install -j
```

I saw the same error in ffmpeg.wasm-core Github Action: https://github.com/ffmpegwasm/ffmpeg.wasm-core/runs/2598825955?check_suite_focus=true seams it's broken since v0.9.0

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.