mirror/freebsd-ports
1
0
Fork 0
mirror of https://git.FreeBSD.org/ports.git synced 2024-11-28 01:06:17 +00:00
Code Issues Releases Activity
a47f4e3179
freebsd-ports/devel/p4api/distinfo

9 lines
532 B
Plaintext
Raw Normal View History

This port was not really usable on i386-5.X due to an updated GCC, since C++ name mangling has changed in an incompatible way. Now that perforce has put FreeBSD 5.X p4api binary on their FTP site, the port can be updated to work on both 4.X and 5.X. The tarball for 4.X was tested with 2.95.4. The tarball for 5.X was tested with 3.3.1. If there were other incompatible name mangling changes in GCC in between, neither will work, so beware. Also, the FreeBSD 4.X p4api tarball checksum has changed. Perforce has confirmed that the new checksum is correct. Approved by: maintainer
2003-09-24 12:18:50 +00:00
MD5 (perforce/03.1/i386-freebsd4/p4api.tar) = 6402ce08a4a49e20cb34a06b30be1dbc
SIZEify. Submitted by: trevor
2004-03-18 00:48:53 +00:00
SIZE (perforce/03.1/i386-freebsd4/p4api.tar) = 1218560
This port was not really usable on i386-5.X due to an updated GCC, since C++ name mangling has changed in an incompatible way. Now that perforce has put FreeBSD 5.X p4api binary on their FTP site, the port can be updated to work on both 4.X and 5.X. The tarball for 4.X was tested with 2.95.4. The tarball for 5.X was tested with 3.3.1. If there were other incompatible name mangling changes in GCC in between, neither will work, so beware. Also, the FreeBSD 4.X p4api tarball checksum has changed. Perforce has confirmed that the new checksum is correct. Approved by: maintainer
2003-09-24 12:18:50 +00:00
MD5 (perforce/03.1/i386-freebsd4/p4api.txt) = f49132a4c5529e1901521ace157ef3ef
SIZEify. Submitted by: trevor
2004-03-18 00:48:53 +00:00
SIZE (perforce/03.1/i386-freebsd4/p4api.txt) = 16266
This port was not really usable on i386-5.X due to an updated GCC, since C++ name mangling has changed in an incompatible way. Now that perforce has put FreeBSD 5.X p4api binary on their FTP site, the port can be updated to work on both 4.X and 5.X. The tarball for 4.X was tested with 2.95.4. The tarball for 5.X was tested with 3.3.1. If there were other incompatible name mangling changes in GCC in between, neither will work, so beware. Also, the FreeBSD 4.X p4api tarball checksum has changed. Perforce has confirmed that the new checksum is correct. Approved by: maintainer
2003-09-24 12:18:50 +00:00
MD5 (perforce/03.1/i386-freebsd5/p4api.tar) = e2a71c3b57212deae1943e84847ffd4f
SIZEify. Submitted by: trevor
2004-03-18 00:48:53 +00:00
SIZE (perforce/03.1/i386-freebsd5/p4api.tar) = 1208320
This port was not really usable on i386-5.X due to an updated GCC, since C++ name mangling has changed in an incompatible way. Now that perforce has put FreeBSD 5.X p4api binary on their FTP site, the port can be updated to work on both 4.X and 5.X. The tarball for 4.X was tested with 2.95.4. The tarball for 5.X was tested with 3.3.1. If there were other incompatible name mangling changes in GCC in between, neither will work, so beware. Also, the FreeBSD 4.X p4api tarball checksum has changed. Perforce has confirmed that the new checksum is correct. Approved by: maintainer
2003-09-24 12:18:50 +00:00
MD5 (perforce/03.1/i386-freebsd5/p4api.txt) = f49132a4c5529e1901521ace157ef3ef
SIZEify. Submitted by: trevor
2004-03-18 00:48:53 +00:00
SIZE (perforce/03.1/i386-freebsd5/p4api.txt) = 16266
Reference in New Issue Copy Permalink