kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #44540
Re: mingw64 build issue.
Ni, they are only cached via the archive artifacts of jenkins, which I
can't reach right now.
fre. 25. sep. 2020 22.39 skrev Wayne Stambaugh <stambaughw@xxxxxxxxx>:
> Is there a repo with with the build configuration so I can see what
> msys2/mingw64 packages are being used in our builds?
>
> On 9/25/20 4:09 PM, Nick Østergaard wrote:
> > I cant reach the build server right now, so I don't know the status, but
> > it is not autoupdated. Mainly updated once in a while after a release
> > has been made with "known good env".
> >
> > fre. 25. sep. 2020 22.02 skrev Wayne Stambaugh <stambaughw@xxxxxxxxx
> > <mailto:stambaughw@xxxxxxxxx>>:
> >
> > I take it we are not getting any nightly build errors for
> msys2/mingw54
> > builds. Do we always use the latest msys2/mingw64 packages for
> nightly
> > builds or are they pinned to a specific version that we know works?
> If
> > it's the latter, where can I find the package list. Maybe that will
> > give me a better idea of which package broke my builds. I suspect JP
> > hasn't run `pacman -Syuu` recently so he may have older build tool
> > packages.
> >
> > On 9/25/20 3:29 PM, Mark Roszko wrote:
> > > I actually got that MSYS2 error awhile back....as for why, I don't
> > know,
> > > I haven't been arsed to rebuild the msys2 install yet again.
> > >
> > >
> > > I'm waiting on vcpkg to merge opencascade which was blocked on
> 32-bit
> > > builds being broken, the MSVC team responded with a workaround to
> the
> > > compiler bug so now its blocked on somebody else having broke
> > vcpkg for
> > > windows (lul)
> > >
> > > There's also a python port upgrade required, someone else managed
> to
> > > beat me to submitting the exact changes I need but that port is
> > pending
> > > merge hopefully once the windows breakage is fixed.
> > >
> > > Then my wxPython port, I'll see if I can sneak it into vcpkg once
> that
> > > python port is merged but it is usable.
> > >
> > > On Fri, Sep 25, 2020 at 3:14 PM Jon Evans <jon@xxxxxxxxxxxxx
> > <mailto:jon@xxxxxxxxxxxxx>
> > > <mailto:jon@xxxxxxxxxxxxx <mailto:jon@xxxxxxxxxxxxx>>> wrote:
> > >
> > > MSVC works great, I really recommend giving it a try. Much
> faster
> > > compile time than msys.
> > >
> > > Seems like Mark will have a solution for wxPython very soon
> too :)
> > >
> > > On Fri, Sep 25, 2020 at 3:10 PM Wayne Stambaugh
> > > <stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>
> > <mailto:stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>>> wrote:
> > >
> > > On 9/25/2020 3:04 PM, jp charras wrote:
> > > >
> > > > Le 25/09/2020 à 19:11, Wayne Stambaugh a écrit :
> > > >> Is anyone else seeing the following error when building
> > with
> > > >> MinGW64/msys2?
> > > >>
> > > >>
> > >
> >
> ../common/libcommon.a(libcontext.cpp.obj):libcontext.cpp:(.text+0x19e):
> > > >> relocation truncated to fit: R_X86_64_PC32 against
> `*ABS*'
> > > >>
> > > >> I did some digging around and it looks like it's a bug
> > in the
> > > context
> > > >> assembly code but I've never seen the error before. I
> > tried
> > > downgrading
> > > >> gcc from 10.2 to 10.1 but no luck. It also happens when
> > > building the
> > > >> 5.1 branch. It doesn't happen when building with
> > MinGW32/msys2.
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Wayne
> > > >
> > > > I am not seeing this issue.
> > > >
> > > > I have a recent (2 weeks) msys install, on a new
> computer,
> > > with W10 -
> > > > 64bits
> > >
> > > Thanks for the feedback. Maybe something got broken
> during an
> > > update.
> > > My msys2 install is quite old so maybe it's time to do a
> clean
> > > reinstall
> > > :(. I guess all development for me will be on Linux until
> > I can
> > > free up
> > > a decent block of time to upgrade msys2 or maybe try out
> > the new
> > > msvc
> > > stuff Mark has been working on.
> > >
> > > Cheers,
> > >
> > > Wayne
> > >
> > > >
> > > >
> > > >> --
> > > >> Jean-Pierre CHARRAS
> > > >
> > > > _______________________________________________
> > > > Mailing list: https://launchpad.net/~kicad-developers
> > > > Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> > > <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx
> > <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>>
> > > > Unsubscribe : https://launchpad.net/~kicad-developers
> > > > More help : https://help.launchpad.net/ListHelp
> > >
> > > _______________________________________________
> > > Mailing list: https://launchpad.net/~kicad-developers
> > > Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> > > <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx
> > <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>>
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > > More help : https://help.launchpad.net/ListHelp
> > >
> > > _______________________________________________
> > > Mailing list: https://launchpad.net/~kicad-developers
> > > Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> > > <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx
> > <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>>
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > > More help : https://help.launchpad.net/ListHelp
> > >
> > >
> > >
> > > --
> > > Mark
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help : https://help.launchpad.net/ListHelp
> >
>
References