-
Notifications
You must be signed in to change notification settings - Fork 187
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
Build failure: undeclared variables #719
Comments
Possibly you need to |
If you've pulled new changes to your local git clone, and you've just typed |
Sure, this is the first thing I tried, using a clean directory. In fact, just now I tried to build manually (no rm -rf ~/tmp
mkdir ~/tmp
cd ~/tmp
git clone https://github.com/arkq/bluez-alsa.git
cd bluez-alsa
autoreconf --install --force
mkdir build
cd build
../configure --enable-cli --enable-aac --enable-systemd
make ... and I get exactly the same error with undeclared symbols.
It's from the latest commit, as I just did
Unfortunately, I can't say that now, as I update packages on that host about once in 2-4 weeks. What I can say for sure is that there was no problem 2 months ago, and there was this same error already 2 weeks ago. If this is the only option to find the issue, I may try to pinpoint the latest working commit when I have time. There is some warning from
|
I suspect this is specific to Arch Linux ARM. I have tried to build on regular Arch Linux host (where I never used bluez-alsa), the build completed normally. |
So I have tried to build some random commit from March, the same error. Yet, this issue began about 3-4 weeks ago, it definitely built normally in March. So I guess something happened with some other package(s) in one of the recent updates in Arch Linux ARM. Sorry, you can probably close the issue (still, if you have any hints on where to look for the cause of the issue, I would appreciate that). |
My first suspicion is that gdbus-codegen is missing or very out of date. On Debian that is in package |
|
This file has the wrong contents. |
Problem solved, thank you. Digging in the direction you provided, I learned about
This gave error:
So I installed Why this error doesn't spring out in the normal build process, and instead some incorrect C file is generated, is a mystery. |
Have been using
bluez-alsa
on Arch Linux ARM for few years now. After one of the recent updates I cannot build new versions any more, getting this error (after some portion of normal compilation output):For reference, here are relevant lines from my
PKGBUILD
bash script:Looks like some header file is missing. The undeclared symbols are not mentioned anywhere else in the src, so I tried to google where
org_bluealsa_pcm1_interface
,org_bluealsa_rfcomm1_interface
andorg_bluealsa_manager1_interface
should be declared, but google gives literally zero results for them.The text was updated successfully, but these errors were encountered: