Bug 258721 - print/freetype2: does not package on main armv6
Summary: print/freetype2: does not package on main armv6
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-desktop (Team)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-25 17:04 UTC by Martin Birgmeier
Modified: 2021-10-03 15:48 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (desktop)


Attachments
portmaster logfile when building print/freetype2 (51.21 KB, text/plain)
2021-09-25 17:04 UTC, Martin Birgmeier
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Birgmeier 2021-09-25 17:04:33 UTC
Created attachment 228175 [details]
portmaster logfile when building print/freetype2

Scenario:
- FreeBSD main at 08b9cc316a319fba95af8bb13b262fe0d5526ec3
- latest ports
- using portmaster to upgrade freetype2 from 2.10.4 to 2.11.0
- using qemu-arm-static and also native on a Raspberry Pi B+

Result:
- Packaging fails with a missing staging directory "/usr/local/share/doc/freetype2"
- Log file attached

Notes:
- The portmaster runs succeeded on 12.2 (latest) amd64 and i386, and on main 08b9cc316a319fba95af8bb13b262fe0d5526ec3 on amd64

-- Martin
Comment 1 Daniel Engberg freebsd_committer 2021-09-25 21:20:55 UTC
This doesn't appear to be something new as the old version also failed 

https://lists.freebsd.org/archives/freebsd-pkg-fallout/2021-September/105389.html (armv6)
https://lists.freebsd.org/archives/freebsd-pkg-fallout/2021-September/110194.html (armv7)
Comment 2 Martin Birgmeier 2021-09-26 06:20:21 UTC
This is strange - here the previous upgrade to 2.10.4 worked without problems.

-- Martin
Comment 3 John Hein 2021-09-27 17:19:56 UTC
Can you try to use a WRKDIRPREFIX that does not have a sym link?  Maybe just define WRKDIRPREFIX to be `realpath $WRKDIRPREFIX`.

It looks like in your build /d is a sym link to /usr/tmp/d (or the other way around).

I think trying to use cpio (with which COPYTREE_SHARE is implemented) to extract to a directory containing sym links some implementations of cpio do not know how to handle that very well.
Comment 4 John Hein 2021-09-27 17:22:13 UTC
(In reply to John Hein from comment #3)
p.s. Normally 'cpio -dumpl' should created any destination directories that don't exist.
Comment 5 Martin Birgmeier 2021-10-03 15:48:53 UTC
You are right, there are some symlinks in the WRKDIRPREFIX.

I have now circumvented the issue by disabling DOCS. For the time being I am closing this report.

-- Martin