On Wed, 28 Jun 2017, at 10:24, David Macek wrote:
> There's only one toolchain and I would assume that the default ABI version
> should always the compatible one.
Unfortunately there's also clang++.
--
Check out the
Hi,
On Fri, 28 Apr 2017, at 07:42, Papa wrote:
> In my Win8.1 is there a way to meke MSYS2 recognized my
> C:\mingw-w64\mingw64\bin . I need to make MSYS2 find gcc so that I can use it
> to build
other applications like FLTK. How can I do this?
> Thanks
You should use the mingw-w64 GCC
On Wed, 22 Mar 2017, at 09:49, Mario Emmenlauer wrote:
> I could narrow down the problem, and actually it seems to be mostly
> a complete ignorance on my side about how unicode, utf8, utf16, wchar
> etc work. I was under the (naiive?) assumption that I could convert a
> std::string to std::wstring
On Thu, 16 Mar 2017, at 23:00, Computer Jock wrote:
> I'm trying to duplicate the code in bash/test that checks that stdout is
> a "terminal". Compiling and running the following:
>
> #include
> #include
> int main( int ac, char **av ) {
>printf( "isatty(stdout): %s\n", isatty(
On Sun, 13 Nov 2016, at 04:38, Andrew Lowe wrote:
> Hi all,
> I teach, amongst other things, C programming to 1st year Engineering
> students here at Curtin Uni in Australia. I've created a nice little
> portable environment with Msys2, conemu2, clang, notepad++ etc, which
> fits on a usb
On Mon, 10 Oct 2016, at 23:50, ralph engels wrote:
> libcxx is still not building, and i fear my C++ fu is not strong enough
> to fix the problems, but maybe someone there can help with that part.
I would love to help out ;) What are the errors?
Hi!
I've noticed that binutils headers (like bfd.h) and its libraries are not in
/mingw{32, 64}/{include, lib} but in /mingw{32, 64}/{include, lib}/binutils. Is
there any specific reason for this?
They are moved at the end of this PKGBUILD:
Hi!
I've ran into the same problem yesterday. Simply creating the
folder using
mkdir /mingw64
fixed it for me. The problem seems to be that pacman only sees the
mingw64.exe file in /.
--
On Tue, 5 Apr 2016, at 13:09, Baruch Burstein wrote:
> Hi,
>
> When compiling with clang(++) from the msys shell, the output is not colored.
> To get colors, I needed to add " -fansi-escape-codes -fcolor-diagnostics".
> How do I make this the default by me? And can this be made the default for
On Thu, 18 Feb 2016, at 22:21, Greg Jung wrote:
> I just tried it, and it is messing with my previously happy usage
> of CMD.exe using target: C:\msys64usr\bin\bash.exe --login -i.
>
> Without that TERM=xterm I don't even have line editing. However
> I can unset TERM in the ./bashrc file and I
On Sun, 22 Nov 2015, at 08:40, Baruch Burstein wrote:
> Is it possible (with this or the old system) to add an "Open MSYS here"
> shortcut to the explorer context menu?
I've programmed smart_msys for that reason: https://github.com/jhasse/smart_cmd
I'm trying to update MSYS 2, this is what I get:
$ pacman --needed -S bash pacman pacman-mirrors msys2-runtime
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: msys2-runtime-devel: requires
2014-06-04 12:08 GMT+02:00 Alexey Pavlov alexey.paw...@gmail.com:
Show more info what not work. I’m not a telepathist.
Show output of:
mount
cd ~ pwd -W
cat /etc/fstab
env
Okay:
jhasse@vaio ~
$ mount
C:/Users/jhass_000 on /home/jhass_000 type ntfs (binary,posix=0,user)
C:/msys64 on /usr
13 matches
Mail list logo
