Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • cerbero cerbero
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • cerberocerbero
  • Issues
  • #31
Closed
Open
Created May 24, 2016 by Bugzilla Migration User@bugzilla-migration

PKG_CONFIG_PATH incorrect for multiarch on Debian

Submitted by Richard Webb

Link to original bug (#766833)

Description

It seems that the PKG_CONFIG_PATH that is set up in cerbero/utils/__init__.py is not always correct.

On the board I am currently using (Wandboard with Ubuntu 14.04) for instance, arch specific pkgconfigs are in /usr/lib/arm-linux-gnueabihf/pkgconfig, while the python script assumes this is always 'usr/lib/%s-linux-gnu/pkgconfig' % arch. This doesn't take into account the Multiarch tuples as specified here:

https://wiki.debian.org/Multiarch/Tuples

I would suggest that this is changed (on Debian) to include the output of the following command:

dpkg-architecture -qDEB_HOST_MULTIARCH

On my system, the above outputs the correct multiarch tuple: arm-linux-gnueabihf.

Happy to attempt a patch if this seems acceptable.

Assignee
Assign to
Time tracking