sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
sandeepkr has joined #m-labs
klickverbot has quit [Ping timeout: 260 seconds]
mumptai has quit [Ping timeout: 272 seconds]
mumptai has joined #m-labs
rohitksingh has joined #m-labs
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 250 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 272 seconds]
Gurty has quit [Ping timeout: 240 seconds]
rohitksingh1 has joined #m-labs
rohitksingh has quit [Ping timeout: 244 seconds]
rohitksingh1 has quit [Ping timeout: 244 seconds]
klickverbot has joined #m-labs
Gurty has joined #m-labs
klickverbot has quit [Ping timeout: 276 seconds]
rohitksingh has joined #m-labs
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 260 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 252 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 250 seconds]
klickverbot has joined #m-labs
rohitksingh has quit [Ping timeout: 276 seconds]
klickverbot has quit [Ping timeout: 260 seconds]
bentley` has quit [Remote host closed the connection]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 260 seconds]
bentley` has joined #m-labs
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 240 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 276 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 276 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 272 seconds]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 244 seconds]
klickverbot has joined #m-labs
<whitequark>
so thisi s really quite interesting
<whitequark>
I can successfully install mingw while in the lab on my win7 vm, but not on the buildbot vm
klickverbot has quit [Ping timeout: 240 seconds]
<whitequark>
and... what mingw installer says is correct. the archive somehow gets truncated.
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 250 seconds]
<kyak>
your provider somehow messes up with files you download?
<whitequark>
no
<whitequark>
since I just downloaded them from another machine through the same connection
<whitequark>
that's amazing.
<whitequark>
mingw-get actually *says* that it has not downloaded the file entirely. it stops at 85% or 99% or smething like that
n00n has joined #m-labs
<n00n>
hi
<whitequark>
hm, mingw-get is not to blame. i get the exact same result in chrome.
<whitequark>
i mean, it *is* to blame in that it doesn't check that what it downloaded wasn't truncated (much less verified a checksum), but it's not the direct cause of the error
<whitequark>
hm, happens even over https.
key2 has quit [Ping timeout: 264 seconds]
<whitequark>
...
<whitequark>
well
<whitequark>
i fixed it.
<whitequark>
i set up nginx to reverse-proxy prdownloads.sourceforge.net heanet.dl.sourceforge.net, force mirror to heanet
<mumptai>
I'd like to build a soc with a small piece of software, run from rom (bram). It looks to me that the builder make a lot of assumption about the system being build (like rom being filled with the bios). Would writing a subclass of the builder, and changing only these aspects, be the way the system is intended to be used?
<whitequark>
bb-m-labs: force build --props=package=openocd conda-win32
<bb-m-labs>
build forced [ETA 38 seconds]
<bb-m-labs>
I'll give a shout when the build finishes
<whitequark>
yeah, tell me again how conda is great.
<whitequark>
anyway, openocd should be done after that's resolved...
<whitequark>
sb0___: how do I test openocd? do you have some easy way to do it? or do I need to install ARTIQ on a VM I can do USB passthrough into and hook it to kc705?
<whitequark>
bb-m-labs: force build --props=package=openocd conda-win32
<bb-m-labs>
build forced [ETA 38 seconds]
<bb-m-labs>
I'll give a shout when the build finishes
<sb0___>
whitequark: yeah, install artiq. will be a nice occasion to check that everything plays nicely together.
<sb0___>
you can btw do what you want with the second kc705
<whitequark>
that's a rather open-ended suggestion
<whitequark>
bb-m-labs: force build --props=package=openocd conda-win64
<bb-m-labs>
build forced [ETA 53 seconds]
<bb-m-labs>
I'll give a shout when the build finishes
<whitequark>
... it worked the third time? why? why did it fail before? we may never know
<whitequark>
seriously though these random network failures really bother me.
<whitequark>
it seems to be something between the host linux (since that works) and guest windows userspace (since that's just, well, windows, it works)