Could this be due to inlining? E.g. a function from libstd that calls an external function gets inlined into another crate (rustc in this case), and now rustc itself needs to be linked with kernel32...?
On Fri, Sep 13, 2013 at 3:29 PM, Kevin Ballard <[email protected]> wrote: > This looks rather similar to the error I was getting with PR #8203, which > was a set of undefined references under Windows. > > > http://buildbot.rust-lang.org/builders/auto-win-32-opt/builds/1212/steps/compile/logs/stdio > > I don't know if it's actually related though. > > -Kevin > > On Sep 13, 2013, at 2:21 PM, Corey Richardson <[email protected]> wrote: > > > Hi all, > > > > I've hit a wall with rustdoc_ng. It fails to build on Windows with > > > http://buildbot.rust-lang.org/builders/auto-win-32-opt/builds/1435/steps/compile/logs/stdio > , > > the error being: > > > > note: > i686-pc-mingw32\stage1\bin\rustc\i686-pc-mingw32\bin\lib.o:fake:(.text+0x68373): > > undefined reference to `SetLastError' > > > > I find this very strange that it manifests in rustdoc_ng. The only > > reason I could see it failing is that it would need to link to > > libstd's dependencies (kernel32 in this case). > > > > Does anyone know what's going on here? > > _______________________________________________ > > Rust-dev mailing list > > [email protected] > > https://mail.mozilla.org/listinfo/rust-dev > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
