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
<cr1901_modern> whitequark: Is linking libLTO supposed to take forever?
sandeepkr has quit [Remote host closed the connection]
kuldeep has quit [Remote host closed the connection]
kuldeep has joined #m-labs
calle__ has joined #m-labs
mumptai_ has quit [Ping timeout: 246 seconds]
kuldeep_ has joined #m-labs
kuldeep has quit [Remote host closed the connection]
<whitequark> cr1901_modern: um, possibly
<whitequark> are you doing a static build or a hared library build?
<whitequark> if former I suggest the latter
<whitequark> also don't forget to build using Ninja and use split-dwarf and link using gold
sandeepkr has joined #m-labs
fengling has quit [Ping timeout: 268 seconds]
fengling has joined #m-labs
<cr1901_modern> whitequark: For once, I *didn't* forget to use Ninja. It was a static build. Ack on split-dwarf, and gold can't do COFF. Curiously, linking libLTO (without any of your suggestions) only takes forever when doing a 64-bit build, not a 32-bit build.
fengling has quit [Ping timeout: 268 seconds]
<GitHub151> [artiq] sbourdeauducq pushed 3 new commits to master: https://git.io/vMqUD
<GitHub151> artiq/master 26e7f68 Sebastien Bourdeauducq: firmware: move clock to libboard
<GitHub151> artiq/master bb056c1 Sebastien Bourdeauducq: firmware: load *_reg correctly
<GitHub151> artiq/master a3041fb Sebastien Bourdeauducq: manual: fix Rust installation instructions
<bb-m-labs> build #291 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/291
<bb-m-labs> build #1190 of artiq is complete: Failure [failed python_unittest_1] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1190 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
fengling has joined #m-labs
fengling has quit [Ping timeout: 268 seconds]
cr1901_modern has quit [Ping timeout: 258 seconds]
fengling has joined #m-labs