Project

General

Profile

Problem building latest 4.1.* builds

Added by Nihil Baxter over 9 years ago

Next build problem with newest 4.1.* builds:

In file included from src/tvhlog.h:31:0,
                 from src/tvheadend.h:43,
                 from src/uuid.c:20:
src/atomic.h: In function ‘atomic_add_u64’:
src/atomic.h:48:23: error: ‘atomic_lock’ undeclared (first use in this function)
src/atomic.h:48:23: note: each undeclared identifier is reported only once for each function it appears in
src/atomic.h: In function ‘atomic_dec_u64’:
src/atomic.h:63:23: error: ‘atomic_lock’ undeclared (first use in this function)
src/atomic.h: In function ‘atomic_pre_add_u64’:
src/atomic.h:78:23: error: ‘atomic_lock’ undeclared (first use in this function)
Makefile:428: recipe for target '/home/hts/build/tvheadend/build.linux/src/uuid.o' failed

Anyone could help? Thx


Replies (39)

RE: Problem building latest 4.1.* builds - Added by Nihil Baxter over 9 years ago

Chef Denker wrote:

I disable some protocols I did not need:
"/configure --arch=ARCH --enable-libffmpeg_static --disable-hdhomerun_client --disable-iptv --disable-satip_client --disable-satip_server && make"

@Fresh Mike
did you "make clean" or "make distclean" in the first place.

Lol, don't know what i did, just tested build process with your configure options (with autobuild_configure_extra) and now it works......

RE: Problem building latest 4.1.* builds - Added by Nihil Baxter over 9 years ago

After some builds compiling fine now there is next error :(

src/libav.h:65:20: error: ‘libav_init’ used but never defined [-Werror]
src/libav.h:64:20: error: ‘libav_set_loglevel’ declared ‘static’ but never defined [-Werror=unused-function]
cc1: all warnings being treated as errors
Makefile:442: recipe for target '/home/hts/build/tvheadend/build.linux/src/main.o' failed
make[2]: *** [/home/hts/build/tvheadend/build.linux/src/main.o] Error 1
make[2]: Leaving directory '/home/hts/build/tvheadend'
debian/rules:11: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/home/hts/build/tvheadend'
debian/rules:5: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2

Didn't change something alt least, error comes with latest builds...
Maybe someone could help?

RE: Problem building latest 4.1.* builds - Added by blue note over 9 years ago

Keep in mind I'm a total newb.

But I built fine this morning, but a while ago I was getting errors and starting again worked. (deleting tvheadend directory, git clone again). I don't know if this is recommended, or if it even helped, but it did seem to fix my problem before.

RE: Problem building latest 4.1.* builds - Added by Nihil Baxter over 9 years ago

Same as me ;) cloning for new will be the next i try, maybe that helps...it did some time :)

RE: Problem building latest 4.1.* builds - Added by Nihil Baxter over 9 years ago

But this time a new clone didn't do the trick :(
So help needed...

RE: Problem building latest 4.1.* builds - Added by Prof Yaffle over 9 years ago

There were some changes to libav.h that introduced the declarations that I think you're seeing break - commit:e6998d5d.

You could try building to that, then the version before, and see if that works...

RE: Problem building latest 4.1.* builds - Added by Nihil Baxter over 9 years ago

Last successful build was v4.1.132 i think.

RE: Problem building latest 4.1.* builds - Added by Prof Yaffle over 9 years ago

... which was commit:5555bc68, or about four before the one I mentioned.

Perexg has just pushed commit:0f0fcd37 in response to this problem - try now...

RE: Problem building latest 4.1.* builds - Added by Nihil Baxter over 9 years ago

Aaargh, every time i have a good working build enviroment something goes wrong....
Now i got this:

dh_pysupport: This program is deprecated, you should use dh_python2 instead. Migration guide: http://deb.li/dhs2p
dh_pysupport: Cannot detect default Python version
debian/rules:5: recipe for target 'binary' failed
make: *** [binary] Error 255
dpkg-buildpackage: Fehler: Fehler-Exitstatus von fakeroot debian/rules binary war 2

I changed nothing after build 4.1.198..
Anyone has an idea?
Thx

RE: Problem building latest 4.1.* builds - Added by Nihil Baxter over 9 years ago

No one got an idea?
On my banana builds fine, on my pi2 sucked....nothing changed, tried with and without autobuild options, tried with new git clone....nothing works...

I've seen this "dh_pysupport: This program is deprecated, you should use dh_python2 instead. Migration guide: http://deb.li/dhs2p" some time before, but never wwas a problem..."migration guide" is somewhat unuseable for me, bad explained and not for noobs like me ;)

RE: Problem building latest 4.1.* builds - Added by Prof Yaffle over 9 years ago

With no real knowledge, my gut feeling is that those errors aren't necessarily the problem - they may simply be warnings, and are the last thing printed out before the build fails. I would guess that there's an error earlier on that might give an idea of a missing library or similar.

Can you pastebin your whole build output, please, to see if there's anything else obvious?

RE: Problem building latest 4.1.* builds - Added by Nihil Baxter over 9 years ago

Really funny, posted that, deleted build folder, did a new git clone...
...and now last build works, with transcode support. Mysterious, yesterday i did the same and build process stops at early point.
The only thing i did between was an reboot, maybe thats it ;)

RE: Problem building latest 4.1.* builds - Added by blue note over 9 years ago

I'm happy with my current build so I haven't been compiling all the time trying to get something bleeding edge where everything I need works :) But I saw this and decided to run a compile to see if I could help out. It's been running a long time so it should be done soon and I'll post back. Note though - I won't be installing because my production box is really production these days.

Oops, I see between posting and reading, that OP's problem is solved. My compile also looks like it will complete fine, although it has not quite yet.

EDIT: No sooner hit post than compile finished fine

(26-39/39)