[Slackbuilds-users] Google-Go-Lang

[John Yost]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/14/2015 01:54 PM, Vincent Batts wrote:
> ick. I'll check on that test failure. In the interim you can set 
> the environment variable RUN_TEST=false to disable the tests at 
> build time.
> 
> http://slackbuilds.org/repository/14.1/development/google-go-lang/
> 
> vb
> 
> On Sat, Mar 14, 2015 at 1:29 PM, John <alleytrotter at gmail.com> 
> wrote:
>> With the recent update the google-go-lang.Slackbuild fails at 
>> "... -- ok      mime/multipart  0.133s --- FAIL: 
>> TestIPv4MulticastListener (0.00s) multicast_test.go:55: First 
>> ListenMulticastUDP on <nil> failed: listen udp 224.0.0.254: 
>> setsockopt: no such device FAIL FAIL    net     2.352s ok 
>> net/http        3.879s ..."
>> 
>> It seem that an internet connection is required for the build to 
>> work. I normally have the following output ports open: --dport 
>> http # Port 80   (Http) --dport https # Port 443  (Https)
>> --dport imap # Port 143  (Imap) --dport imaps # Port 993  (Imaps)
>> --dport pop3 # Port 110  (Pop3) --dport smtp # Port 25   (Smtp)
>> --dport smtps # Port 465  (Smtps) --dport ftp-data # Port 20
>> (Ftp Data) --dport ftp # Port 21   (Ftp) --dport ssh # Port 22 
>> (Ssh) --dport nntp # Port 119  (News groups) --dport 5222 # Port 
>> 5222 (Jabber) --dport 6881:6889 # Port 6881 a 6889 (Bittorrent) 
>> --dport 873 # Port 873  (rsync) --dport 43 # Port 43   (whois) 
>> --dport 11371 # Port 11371   (pgp_key) With which it will not 
>> build. Does anyone know what port must be open so the 'build'
>> can call the mothership and get permission to allow Go to build?
>>  Shouldn't it be stated in the 'requires'? TIA
>> 
>> John David Yost AlleyTrotter pub   2048D/F3BDEB55 2014-05-23 
>> [expires: Never]
>> 
>> 
>> 
>> -- Life expectancy in a firefight Radio Man 3 seconds Medic 7 
>> seconds Officer whenever they get around to it.
>> 
>> _______________________________________________
>> SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org
>>  http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>  Archives - 
>> http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - 
>> http://slackbuilds.org/faq/
>> 
>> 
> _______________________________________________ SlackBuilds-users 
> mailing list SlackBuilds-users at slackbuilds.org 
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users 
> Archives - 
> http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - 
> http://slackbuilds.org/faq/
> 
Yes that is how I built it this time and the first time I built Go
Just thought you would like to know about the requirement.
My build system I use is a clean Slackware64-14.1 without a network
configured as I think it keeps things clean.
Thanks
John

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iF4EAREIAAYFAlUEegIACgkQLHr2vvO961X8GgEAtWh1d+JJt3YFujJaIWOTThd3
vgAKmkGYmNRumqD1qvMBAOfsMc5rF9pjUB0itJw0fiAgUKAS1sG9m6PjqJQVpmSV
=JzZa
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xF3BDEB55.asc
Type: application/pgp-keys
Size: 2312 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150314/80acc530/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xF3BDEB55.asc.sig
Type: application/octet-stream
Size: 96 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150314/80acc530/attachment-0001.obj>