Bug newclock4 build fail '--with-platform=raspberry-pi'; "lgpg-error" not found
#16
(2016-10-14, 08:54)abga Wrote: Apparently I got over it by manually copying the following dependencies from /opt/vc/include :

Thank you for this facepalm moment.

google: CFLAGS
google: CPPFLAGS
google: CXXFLAGS


Code:
export CFLAGS=-I/opt/vc/include
export CXXFLAGS=-I/opt/vc/include
export LDFLAGS=-L/opt/vc/lib
(2016-10-14, 08:54)abga Wrote: I was wondering why is the pretty standard /opt/vc folder not checked during the configure script

/opt/vc is absolutely NOT standard.
Before making such statements please research about debian fs hierachy.
http://www.tldp.org/LDP/Linux-Filesystem...l/opt.html
Reply
#17
You're welcome! but don't abuse it, try some constructive activity instead.

Using environmental C/CXX/FLAGS -I breaks the configure script! Try it! ... and LDFLAGS doesn't really help - please read through my post.

Ups, I thought /opt/vc IS quite a standard when it comes to Raspberry Pi and the main supporting distros, apart from Ubuntu, sorry but I can't stand my hand, which will soon become Redmond, a huge/slow/lazy mess Nod

It wasn't a statement, it was a question - maybe a suggestion for some more sensible/perceptive. Sorry, not curious about "Debilan" either, I just mount the fresh Jessie image, once Raspberry releases it and nick all interesting stuff from it (kernel/modules and /opt/vc).
Reply
#18
If one will manually update Raspberry userland from:
https://github.com/raspberrypi/userland.git

and build it natively, he'll learn that it will get built and installed in /opt/vc

The STANDARD destination looks like being hardcoded in the cmake file:

cat /kit/userland/makefiles/cmake/vmcs.cmake | grep -e "/opt"
SET(VMCS_INSTALL_PREFIX "/opt/vc" CACHE PATH "Prefix prepended to install directories" FORCE)
# also put it in /opt/vc for access by install script
# provide headers the libraries need in /opt/vc too

Now, if one is used with this modern apt-get or more appropriate apt-you-never-know-what-you-get, since you don't get a build script attached with the package and have no clue how it was built - ergo not comprehensible/reproducible, which also contravenes with the Linux Opensource Philosophy, not to mention common sense, then such "STANDARD" details are really not transparent.
Wink
Reply
#19
Last one, just for the reference - C/CXX/FLAGS -I breaking the initial ./configure script:

http://forum.kodi.tv/showthread.php?tid=...pid2426330

I don't have time to parse/audit all the build scripts, and I'm sorry for that, but it looks like they were not designed for a native build. Might be helpful to inform the users not to attempt that.

- thanking again the ones that resolved the issue reported in this thread
- I'm unsubscribing
Reply
#20
Sorry for not keeping my promise, but I've found something helpful for anyone interested, that really works and it wasn't to be found on google but through some cross-referenced sites:

http://wiki.mitsted.dk/?page=RPi_Resources
(it contains also some additional and actual (Kodi 17 included) bug-fixing for successfully compiling Kodi for RaspberryPi )

It looks like the needed/missing compiler environment parameters, that actually work and are not breaking the configure script were:

export C_INCLUDE_PATH=/opt/vc/include:/opt/vc/include/interface/vcos/pthreads
export CPLUS_INCLUDE_PATH=/opt/vc/include:/opt/vc/include/interface/vcos/pthreads
export LDFLAGS="-L/opt/vc/lib"

abga has left the building!
Reply

Logout Mark Read Team Forum Stats Members Help
newclock4 build fail '--with-platform=raspberry-pi'; "lgpg-error" not found1