mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #2] OSX 10.13 build failed #3
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @truatpasteurdotfr on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/2
Originally assigned to: @walker0643 on GitHub.
Operating Systems
macmini:~ tru$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.13.2
BuildVersion: 17C205
Barrier Version
git version:
33b81742b5barrier: 1.9.0-snapshot.b1-33b81742
Steps to reproduce bug
Other info
errors:
@walker0643 commented on GitHub (Feb 13, 2018):
Fixed in
f07070f7f9. Please test.@truatpasteurdotfr commented on GitHub (Feb 19, 2018):
but it builds fine :D
@truatpasteurdotfr commented on GitHub (Feb 19, 2018):
trying to push a 10.13 target yields:
with this warning:
@walker0643 commented on GitHub (Feb 20, 2018):
Unfortunately the previous two post of yours, tru, are highlighting known issues with the build. They both stem from needing to support more releases than just the latest OSX (currently 10.13). As it stands right now the source tree will create builds that are compatible with 10.9 through 10.13 even though the builds are rather noisy with respect to warnings.
Before we close this issue would you mind confirming that the program itself runs well on your OSX test box(es)? Thanks!
@walker0643 commented on GitHub (Feb 23, 2018):
Got confirmation from tru via IRC. Closing.