linuxmint / linuxmint/warpinator

FTBFS on ppc64 arch

Open
#227 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.6k
Forks
115
PR merge metrics
No merged PRs in 30d

Description

Distribution

LMDE 6 Faye

Package version

1.8.8

Frequency

Always

Bug description

I tried building warpinator from source but did not manage to get it built. I received the following error:

Installing data/org.x.Warpinator.appdata.xml to /build/warpinator-1.8.8/debian/tmp/usr/share/metainfo
Installing data/warpinator-send.nemo_action to /build/warpinator-1.8.8/debian/tmp/usr/share/nemo/actions

ERROR: File 'src/grpc' could not be found
FAILED: meson-internal__install
/usr/bin/meson install --no-rebuild
ninja: build stopped: subcommand failed.
dh_auto_install: error: cd obj-powerpc64-linux-gnu && DESTDIR=/build/warpinator-1.8.8/debian/tmp LC_ALL=C.UTF-8 ninja install returned exit code 1
make: *** [debian/rules:4: binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Regards,
Jeroen

Steps to reproduce

I built the source package from git in a Debian sid ppc64 sandboxed chroot.

Expected behavior

It should build correctly as I have all build depends.

Additional information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the source-package build in the Debian sid ppc64 chroot and start with debian/rules and the Meson install step that reports the missing src/grpc file. Check how the src/grpc path is referenced during installation; done means the ppc64 package completes its build and install without the FTBFS error.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.