Bug 184363 - [patch] misc/compat8x enable sparc64
Summary: [patch] misc/compat8x enable sparc64
Status: Closed Not Accepted
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Mark Linimon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-28 23:30 UTC by craig001
Modified: 2015-12-28 17:28 UTC (History)
3 users (show)

See Also:


Attachments
file.diff (1.56 KB, patch)
2013-11-28 23:30 UTC, craig001
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description craig001 2013-11-28 23:30:01 UTC
sparc64 support was dropped from misc/compat8x currently when trying to compile from ports we get "...only for i386 amd64, while you are running sparc64."

I have updated the distfile, distinfo, Makefile, and created a pkg-plist-sparc64.

Libs where pulled from a compiled 8.4-RELEASE.  I used compat8x-sparc64-8.3.803000.201209.tar.bz2 as a reference.

I have tried a few make, make install, make deinstall

distfile is available from - http://bsdtec.com/freebsd/distfiles/compat8x-sparc64-8.4.804000.201310.tar.xz

Fix: see attached patch

Patch attached with submission follows:
How-To-Repeat: try to compile misc/compat8x from ports on a sparc64 machine.
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-11-28 23:30:11 UTC
Responsible Changed
From-To: freebsd-ports-bugs->garga

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Michael Moll freebsd_committer freebsd_triage 2015-11-29 19:09:08 UTC
does anybody still need misc/compat8x for sparc64? If there are no objections I would close this ticket.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2015-11-29 22:42:13 UTC
At this point only a handful of ports depend on compat8x to start with:

www/thundercache (x86 only)

Uh, actually, rechecking, that's the only one :-)

There are not even that many ports that remain depending on compat9x.  Almost all are haskell ports.  One notable exception is www/opera but that is also x86-only.
Comment 4 Michael Moll freebsd_committer freebsd_triage 2015-11-29 22:58:06 UTC
alright, closing then...
Comment 5 Konstantin Belousov freebsd_committer freebsd_triage 2015-11-30 08:30:19 UTC
(In reply to Mark Linimon from comment #3)
The purpose of the compatNx ports is to allow the binaries left on the user machine to continue working after the major version upgrade.  The port is almost irrelevant for the binaries coming from the ports/packages, since most of them can be recompiled or reinstalled.

It is for unique and obscure stuff which happens to appear from the unknown or lost sources on someone box.   Please do not use the ports dependencies to evaluate the need of the compatNx.
Comment 6 Mark Linimon freebsd_committer freebsd_triage 2015-11-30 13:51:52 UTC
OK, fair enough.
Comment 7 craig001 2015-11-30 16:53:30 UTC
+1 for Konstantin comment

I initially fixed these ports because I upgraded a few jails running some legacy binaries.
Comment 8 Michael Moll freebsd_committer freebsd_triage 2015-12-28 17:28:25 UTC
see #184379