Chromium build fails with undefined references to libiconv at linking stage

36 views
Skip to first unread message

punishm...@gmail.com

unread,
Sep 12, 2021, 1:43:26 AMSep 12
to Chromium-dev
As per title, I have not been able to build the latest version of Chromium for two days now, the build always fails at the linking stage with errors about undefined references to libiconv

Reproducible by doing the following:
(1) Build the latest Chromium from source
(2) Build fails at the linking stage with an error about undefined references to libiconv

[51144/51144] LINK ./chrome
FAILED: chrome 
python3 "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" -- ../../third_party/llvm-build/Release+Asserts/bin/clang++ -Wl,--version-script=../../build/linux/chrome.map -fuse-ld=lld -Wl,--fatal-warnings -Wl,--build-id -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,--icf=all -Wl,--color-diagnostics -Wl,--no-call-graph-profile-sort -m64 -no-canonical-prefixes -Wl,-O2 -Wl,--gc-sections -rdynamic -nostdlib++ --sysroot=../../build/linux/debian_sid_amd64-sysroot -Wl,-z,defs -Wl,--as-needed -pie -Wl,--disable-new-dtags -o "./chrome" -Wl,--start-group @"./chrome.rsp"  -Wl,--end-group  -ldl -lpthread -lrt -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lnss3 -lnssutil3 -lsmime3 -lplds4 -lplc4 -lnspr4 -latk-1.0 -latk-bridge-2.0 -lcups -lgio-2.0 -ldrm -ldbus-1 -lresolv -lexpat -luuid -lxcb -lxkbcommon -lm -lz -lX11 -lXcomposite -lXdamage -lXext -lXfixes -lXrender -lXrandr -lXtst -lgbm -lwayland-client -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -lcairo -lXi -lpci -lasound -latspi -lgtk-3 -lgdk-3 -lcairo-gobject -lgdk_pixbuf-2.0 -lxshmfence
ld.lld: error: undefined symbol: libiconv_close
>>> referenced by oss_utils.cc
>>>               obj/third_party/maldoca/maldoca-ole/oss_utils.o:(maldoca::utils::BufferToUtf8::Init(char const*))
>>> referenced by oss_utils.cc
>>>               obj/third_party/maldoca/maldoca-ole/oss_utils.o:(maldoca::utils::BufferToUtf8::~BufferToUtf8())
>>> referenced by oss_utils.cc
>>>               obj/third_party/maldoca/maldoca-ole/oss_utils.o:(maldoca::utils::BufferToUtf8::~BufferToUtf8())
>>> referenced 3 more times

ld.lld: error: undefined symbol: libiconv_open
>>> referenced by oss_utils.cc
>>>               obj/third_party/maldoca/maldoca-ole/oss_utils.o:(maldoca::utils::BufferToUtf8::Init(char const*))

ld.lld: error: undefined symbol: libiconv
>>> referenced by oss_utils.cc
>>>               obj/third_party/maldoca/maldoca-ole/oss_utils.o:(maldoca::utils::BufferToUtf8::ConvertEncodingBufferToUTF8String(absl::string_view, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >*, int*, int*, int*))
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.


Last known working build was made on 4 Sept.

gn args are as follow:
ffmpeg_branding="Chrome"
proprietary_codecs=true
enable_widevine=true
blink_symbol_level=0
symbol_level=0
treat_warnings_as_errors=false
target_cpu="x64"
use_ozone=true
ozone_platform_wayland=true
ozone_platform_x11=true
ozone_auto_platforms=false
use_xkbcommon=true
use_system_minigbm=true
use_system_libwayland=true
use_system_libdrm=true
use_wayland_gbm=true
is_debug=false
enable_nacl=false
dcheck_always_on=false

Does anyone know what is going on? 

Nico Weber

unread,
Sep 12, 2021, 11:37:46 AMSep 12
to punishm...@gmail.com, Chromium-dev
I left a comment on the bug.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/32563afb-6a41-4653-b43b-27b9f836181an%40chromium.org.
Reply all
Reply to author
Forward
0 new messages