PLATFORMID is set in debian/rules:
debian/rules:569:PLATFORMID := $(shell grep PLATFORMID
debian/vars.$(DEB_HOST_ARCH) | cut -d"=" -f2)
and unsurprisingly:
./debian/vars.i386:1:PLATFORMID=linux_x86
./debian/vars.s390x:1:PLATFORMID=linux_s390x
./debian/vars.amd64:1:PLATFORMID=linux_x86_64
I'm wondering whether DEB_HOST_ARCH could be always (incorrectly) expanded to
amd64 in the context of the autopkgtest runner?
** Changed in: libreoffice (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => High
** Changed in: libreoffice (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1712873
Title:
autopkgtests failures on i386 and s390x for 5.4.0, assumes wrong
architecture
Status in libreoffice package in Ubuntu:
Triaged
Bug description:
Looking at autopkgtests failures on i386 and s390x for
1:5.4.0-0ubuntu2 in artful-proposed (logs attached).
The following linker failure:
/usr/bin/ld: cannot find -ljawt
is due to $JAVA_PROC_TYPE being incorrect ("amd64" instead of "i386"
or "s390x"), and thus $LINK_JAVA_LIBS has the incorrect architecture
in its path and the linker doesn't find libjawt.so.
This is likely caused by $PROCTYPE being incorrect, which itself is
set from $PLATFORMID.
There are other hints that $PROCTYPE has a wrong value in the logs,
even though that doesn't appear to make the tests fail:
[…]
mkdir -p
/tmp/tmp.OSVUCMLVqv/out/sdk/LINUXexample.out/misc/CppComponentSample/Linux_x86_64
[…]
which means $UNOPKG_PLATFORM has an incorrect value, set from
$PROCTYPE.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1712873/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
