The distfile for this port is unfetchable if ARCH=amd64. The reason for this is that the rpm packager decided to ARCH=x86_64 instead of amd64 in their naming convention. This patch will fix the issue. How-To-Repeat: cd ${PORTSDIR}/x11-toolkits/linux-gtk2 && make ARCH=amd64 fetch
Responsible Changed From-To: freebsd-ports-bugs->freebsd-emulation Over to maintainer http://www.freebsd.org/cgi/query-pr.cgi?pr=91911 Adding to audit trail from misfiled PR ports/91941: Date: Wed, 18 Jan 2006 09:27:58 +0100
This port still is not working correctly, it tries to fetch "gtk2-2.4.14-4.fc3.3.amd64.rpm," which does not exist.. if it should be fetching the i386 distfile, the port needs to be modified to do this. I will work on a patch to get around this.. one thing that comes to mind is not using ARCH in the distfile names. Using something like SUB_ARCH will allow us to JUST change the DISTNAME, and not effect the rest of the build process. Cheers, Frank
Am Wed, 08 Feb 2006 12:38:34 -0500 schrieb Frank Laszlo <laszlof@vonostingroup.com>: > This port still is not working correctly, it tries to fetch > "gtk2-2.4.14-4.fc3.3.amd64.rpm," which does not exist.. if it should be > fetching the i386 distfile, the port needs to be modified to do this. I > will work on a patch to get around this.. one thing that comes to mind > is not using ARCH in the distfile names. Using something like SUB_ARCH > will allow us to JUST change the DISTNAME, and not effect the rest of > the build process. Let me guess: you are trying to install acroread7 while linux-gtk2 isn't installed. You get this error message because of a bug in bsd.port.mk (or in the acroread7 port, depending on your point of view...). The linux-gtk2 port is just fine. Install it by hand instead of a dependency of the acroread port and it should work just fine. Bye, Alexander. -- Loose bits sink chips. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/
I have finished my investigation of this issue. and It seems that the linux ports are to blame. they overwrite ARCH on multiple occasions when MACHINE_ARCH=amd64. This causes issues with other ports, such as the distfiles are unable to be fetched. I have written numerous patches[1] and tested them in my own environment. All is now working as expected. I have CC'd the freebsd-emulation list on this email, as I would like others to see/test these patches. Once again, these will only effect systems running FreeBSD with an amd64 ARCH. Please contact me with any questions/concerns. Regards, Frank [1] http://www.franksworld.org/~laszlof/linux_patches
I have submited a couple additional patches[1], one for devel/linux_devtools, and one for emulators/linux_base-debian. Please review these as well. I believe that is all the ports that behave unexpectedly due to this mistake. Regards, Frank [1] http://www.franksworld.org/~laszlof/linux_patches
Responsible Changed From-To: freebsd-emulation->netchild The upcomming update of the default linux base port depends on patches, which also will fix this problem. Since I will be the committer which commits this, I take this PR to have a better overwiev of related PR's.
State Changed From-To: open->closed This is fixed with the new linux infrastructure.