Hi
On 28. Sep 2021, at 16:39, Eliot Miranda eliot.miranda@gmail.com wrote:
On Sep 28, 2021, at 5:39 AM, Marcel Taeumel marcel.taeumel@hpi.de wrote:
Hi Bruce --
What debian package is it trying to find the cflags for?
glib, pango, cairo, ... something like this:
UNICODE_PLUGIN_CFLAGS = -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 UNICODE_PLUGIN_LIBS = -lpangocairo-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lcairo
We will have to elaborate the makefiles to remove the processor specificity. An if-then-elif-then Chan is needed fir the processor specificity. arm64 and x86_64 are only two of several possibilities here.
What you see there was provided by pkg-config. it is linux-specifc and necessary due to glib (not to be confused with glibc)
these path are not in the repo.
I am building the Virtend vm on Apple silicon and x86_64 and have to do similarly.
But more concerning is the glibc version. The entire vm must use the same glibc version and so if we want to be able to specify it we need a variable name and that needs to be used across the entire vm build.
Again let me suggest that using static makefiles is far easier and faster to implement and debug this kind of flexibility rather than the autoconf nightmare we endure now.
They confuse the hell out of me. And break profoundly once any of the involved 3drpartys (linux,distro,windors,apple) changes any path…
-t
Best, Marcel
Am 28.09.2021 13:18:22 schrieb Bruce O'Neel bruce.oneel@pckswarms.ch:
Hi,
Nope, you are right, I am one commit behind.
I'll check that out and build. Thanks!
bruce
On 2021-09-28T13:06:40.000+02:00, Tobias Pape wrote:
Hi Bruce
On 28. Sep 2021, at 12:44, Bruce O'Neel wrote:
HI,
On my arm64 system the unicode plugin is disabled.
But on my two Raspberry PI Arm 32 systems, one old and one new, the unicode plugin tries to build but fails because @UNICODE_PLUGIN_CFLAGS@ is not substituted.
What debian package is it trying to find the cflags for?
It should be, i missed the reconfigure, but commited that… Can you check you're on the latest checkout? -t
Thanks.
bruce
Hi,
Nope, you are right, I am one commit behind.
I'll check that out and build. Thanks!
bruce
On 2021-09-28T13:06:40.000+02:00, Tobias Pape Das.Linux@gmx.de wrote: Hi Bruce
On 28. Sep 2021, at 12:44, Bruce O'Neel bruce.oneel@pckswarms.ch wrote:
HI,
On my arm64 system the unicode plugin is disabled.
But on my two Raspberry PI Arm 32 systems, one old and one new, the unicode plugin tries to build but fails because @UNICODE_PLUGIN_CFLAGS@ is not substituted.
What debian package is it trying to find the cflags for?
It should be, i missed the reconfigure, but commited that… Can you check you're on the latest checkout? -t
Thanks.
bruce