AdaCore / AdaCore/ada_libfswatch

undefined reference to `libintl_bindtextdomain'

Open
#6 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ada
Stars
0
Forks
3
PR merge metrics
No merged PRs in 30d

Description

I have built this against libfswatch 1.13.0 without problems. Using FreeBSD 16 (-CURRENT as of Mar 2026) on amd64.

When building downstream project such as ada_language_server on FreeBSD the final link stage refers to libfswatch.a, but the linker cannot find important symbols such as:

undefined reference to `libintl_bindtextdomain'
undefined reference to `std::bad_array_new_length::bad_array_new_length()
undefined reference to `std::__1::mutex::~mutex()

It seems that libintl and libstdc++ are not linked.

libtool libfswatch.la tells us we shall include the following flags when linking the fswatch library:

> grep ^dependency_libs ./libfswatch/src/libfswatch/libfswatch.la
dependency_libs=' -R/usr/local/lib  -L/usr/local/lib -lintl -lpthread'

/usr/local/lib is FreeBSD specific, but the dependency on intl and threads is universal.

Shouldn't those flags go into the GPR file to let Ada Language Server know it shall use additional flags? How does it work on your platforms?

linking step log

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the libfswatch.la dependency_libs entry and the linked linking step log, then inspect the repository's GPR file and reproduce the final link on FreeBSD 16. Done means the Ada Language Server link resolves the libintl, C++ standard library, and thread symbols without requiring undocumented platform-specific flags.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.