https://bugs.freedesktop.org/show_bug.cgi?id=101614
George Kyriazis changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=101614
Bruce Cherniak changed:
What|Removed |Added
Assignee|mesa-dev@lists.freedesktop.
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #15 from Trevor SANDY ---
Hi Guys !
I would like to come back on this ticket because, for me, the problem I
reported is completely fixed by the patch George Kyriazis provided. However, I
noticed his patch is
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #14 from Emil Velikov ---
George, I'm only build-testing those, I have no setup to actually test those.
No idea on the on the symbols part. In general scons or mingw (the w64 of
course), Brian and Jose are
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #13 from Emil Velikov ---
(In reply to Trevor SANDY from comment #10)
> Ok, Thanks to George's patch (0001-mingw-fixes.patch), the behaviour
> reported in this ticket is fixed.
>
> I applied the set below
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #12 from George Kyriazis ---
Emil,
you said that cross compiling software drivers on arch works for you.
Have you tried running the generated binaries? I've created a patch for
Trevor, but for some
https://bugs.freedesktop.org/show_bug.cgi?id=101614
George Kyriazis changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://bugs.freedesktop.org/show_bug.cgi?id=101614
Trevor SANDY changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #9 from Emil Velikov ---
Trevor, please try and get [ideally] all of the patches upstreamed. Be that in
mesa[1] or the respective project. Frédéric Devernay may be able to lend a
hand?
Any of your local
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #8 from Trevor SANDY ---
MSYS2 Setup Details - FYI
MSYS2 Install:
• Download and install msys2-x86_64-.exe (see instructions at
http://www.msys2.org/)
• Install to C:\msys64 (be sure to check 'Run MSYS2
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #7 from Trevor SANDY ---
You can see in options listing of the logged output I posted all the component
versions of my MSYS/MINGW dev env.
I'm using...
- MSYS bash at /usr/bin
- MSYS python at /usr/bin (#02
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #6 from George Kyriazis ---
I tried compiling just osmesa, but still got the same issue.
I've always had trouble using bash with python on windows (bash from Cygwin).
Regardless of whether I use python
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #5 from Trevor SANDY ---
George,
One more point. I did not use the windows command environment. My toolchain is
MSYS2/Mingw64. My command environment is Bash. Looking at your command output,
it looks like
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #4 from Trevor SANDY ---
George,
I haven't personally experienced this error but I did come across it in several
places. In fact, Bug 94072 - error: The command line is too long when building
MESA on Windows
https://bugs.freedesktop.org/show_bug.cgi?id=101614
George Kyriazis changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #2 from Trevor SANDY ---
Hi George,
Unfortunately no, I have not.
My solution is Qt-based and I use QMake across all platforms (OSX, Linux and
Win). For Win, I use the MinGW/GCC toolchain.
Just the check,
https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #1 from George Kyriazis ---
Trevor,
have you tried compiling with devenv? We don't have a problem compiling 17.1.3
there.
We haven't tried compiling with mingw.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=101614
Bug ID: 101614
Summary: OSMesa 17.1.3 simd16intrin build FAIL on Win/MinGW -
'expected initializer before _simd16_setzero_ps ...'
Product: Mesa
Version: 17.1
Hardware:
18 matches
Mail list logo