arthur | 11 Jan 20:50 2016
Picon

git installation

Happy New Year, List!

I used to install my PC with mingw-get but recently I tried a fresh 
installation of MinGW with the GUI installer. I installed the 
'mingw32-base', 'msys-base' and 'mingw-deleloper-toolkit'. Then in MSYS 
I have cvs (from MSYS) and svn (from my TortoiseSVN) but not git.

I know I can install cyg-win or git-for-windows to get git to my PC, but 
I think there may be a more clean way to add only git to my MinGW32/MSYS 
without other MSYS/MinGW64 files. What is the recommended way to add git.

Thanks,

Arthur

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
waterlan | 9 Jan 09:35 2016
Picon
Picon

porting scripts

Hi,

I looked at the latests mingw32 package upgrades (gettext and binutils) 
and I could not find a copy of the porting scripts in the src packages. 
I think they should be in there, because without them it becomes extra 
difficult for other people to create an upgrade.

I like the approach of the msys2 project, where all porting scripts are 
in a git repository. This makes it easy for people to contribute. It 
also makes it a lot easier if you would like to do a mass rebuild with a 
new gcc version.

regards,

--

-- 
Erwin Waterlander
http://waterlan.home.xs4all.nl/

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
waterlan | 5 Jan 07:05 2016
Picon
Picon

ugrade mingw32-libunistring problem

Hi,

I upgraded mingw32-libunistring to version 0.9.6, but in the catalogue 
the version sticks to 0.9.3.

I updated file contrib/mingw32-libunistring.xml, and did a normal build.
Only contrib/issue.log changed, and there was only one unpublished file: 
contrib/unpublished/mingw32-libunistring.xml.lzma.
I'm not sure if this is normal. Normally common/issue.log also changes, 
and there are new packet list lzma files generated.

I did upload everything.

regards,

--

-- 
Erwin Waterlander
http://waterlan.home.xs4all.nl/

------------------------------------------------------------------------------
waterlan | 3 Jan 23:30 2016
Picon
Picon

mingw32-ncurses 6.0

Hi,

I uploaded a new package: mingw32-ncurses 6.0. You can install it with 
mingw-get.

ncurses 6.0 improved a lot for Windows since 5.9, but there are still 
issues (which are not in PDCurses).
* To make it work in Console(2) you have to set the NCURSES_CONSOLE2 
environment variable.
* It doesn't work at all in ConsoleZ.
* You may see tremble in the screen while it is redrawing.

Advantage over PDCurses:
* support for Unicode combining characters.

regards,

--

-- 
Erwin Waterlander
http://waterlan.home.xs4all.nl/

------------------------------------------------------------------------------
Earnie | 3 Jan 20:47 2016
Picon
Picon

MSVCRT.DLL is no longer stated as the "Known DLL"

The read for MSVC 2015 removes the "Knwon DLL" wording.  Compare the
pages at
https://msdn.microsoft.com/en-us/library/abx4dbyh(v=vs.140).aspx and
https://msdn.microsoft.com/en-us/library/abx4dbyh(v=vs.120).aspx

Just wanted to give a heads up to the changes in documentation.
--

-- 
Earnie

------------------------------------------------------------------------------
Erwin Waterlander | 20 Nov 22:24 2015
Picon
Picon

new dos2unix uploaded

Hi,

I uploaded a new version (7.3.2) of dos2unix for msys and mingw.
Somebody can update the catalog. I have no permission.

best regards,

Erwin

------------------------------------------------------------------------------
NightStrike | 3 Aug 05:48 2015
Picon

mingw symlink

I tried building the toolchain for the first time in a long time, and
I see this is still an issue:

The directory that should contain system headers does not exist:
  /opt/mw64/sysroot/mingw/include

Is it at all possible to get rid of that dependency?  As I recall,
that was a holdover from mistakes made eons ago.  I get that "/mingw"
is the Windows equivalent of "/usr", but the issue here is that the
build system extends the sysroot variable.  It looks for
$sysroot/usr/include or $sysroot/mingw/include instead of just
$sysroot/include.

Does --with-build-sysroot make this go away?  Or, can it be made to do so?

------------------------------------------------------------------------------
Keith Marshall | 17 May 10:03 2015
Picon
Picon

Naming of multiple inclusion guards in MinGW headers

Guys,

I've noticed that we have some headers guarded by macros named according
to a _FOO_H_ convention (with a trailing underscore), while others
conform to _BAR_H (without the trailing underscore); we really need to
standardize on one or the other.

I have a mild preference for the latter, but can accept the former; I
cannot accept indefinite persistence of the present inconsistency.

Any strong contrary opinions, before I embark on a standardization
campaign?  (If you disagree, and don't speak up *now*, I will begin to
move toward adoption the _BAR_H style, just as soon as I find a window
of opportunity; (which may be two or three months hence).

--

-- 
Regards,
Keith.

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
Earnie | 6 Jan 00:04 2015
Picon
Picon

Re: What purpose does __NO_ISOCEXT serve?

> -----Original Message-----
> From: Earnie 
> Sent: Monday, December 22, 2014 4:03 PM
> To: 'MinGW Devlopers Discussion List'
> Subject: RE: [MinGW-dvlpr] What purpose does __NO_ISOCEXT serve?
> 
> > -----Original Message-----
> > From: Keith Marshall
> 
> >
> > IMO, it is an aberration.  AFAICT, it is another mechanism, in
> > addition to __STRICT_ANSI__, for suppressing declarations which are
> > not expected to be specified in the ISO-C namespace.  In the mingwrt
> > headers, I see several instances where non-ISO-C declarations are
> > conditionalized on
> !__NO_ISOCEXT,
> > but many more where !__STRICT_ANSI__ is used (abused?) for the same
> > purpose; there seems to be no rational explanation for the particular
> choice
> > made, in each instance.
> >
> > I'd like to get rid of this aberration.  Unfortunately, there seems to
> > be
> an
> > abundance of anecdotal evidence, on the internet, for it having leaked
> into user
> > space, (in spite of the double underscore prefix, which
> > *should* mark it as reserved for internal use by the runtime
> implementation).
> > Thus, I propose folding it into a _mingw.h feature test
(Continue reading)

Keith Marshall | 21 Dec 14:58 2014
Picon
Picon

What purpose does __NO_ISOCEXT serve?

IMO, it is an aberration.  AFAICT, it is another mechanism, in addition
to __STRICT_ANSI__, for suppressing declarations which are not expected
to be specified in the ISO-C namespace.  In the mingwrt headers, I see
several instances where non-ISO-C declarations are conditionalized on
!__NO_ISOCEXT, but many more where !__STRICT_ANSI__ is used (abused?)
for the same purpose; there seems to be no rational explanation for the
particular choice made, in each instance.

I'd like to get rid of this aberration.  Unfortunately, there seems to
be an abundance of anecdotal evidence, on the internet, for it having
leaked into user space, (in spite of the double underscore prefix, which
*should* mark it as reserved for internal use by the runtime
implementation).  Thus, I propose folding it into a _mingw.h feature
test initialization, (_POSIX_C_SOURCE perhaps?), and replacing its use
elsewhere, with the appropriate *enabling* feature test.

Thoughts?  Objections?

--

-- 
Regards,
Keith.

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
Keith Marshall | 20 Nov 17:41 2014
Picon
Picon

Please vote: should we fix or drop the usleep() function?

Guys,

Looking in ChangeLog, I see that (a broken) implementation of usleep()
was added to mingwrt in 2008, just about the time that POSIX.1003-1
dropped it, and removed all references to it from the standard.  So...

1) Should we go along with POSIX, and similarly drop it, or...
2) Retain it, but mark it as deprecated?

I'm of two minds, but if we do decide on (2), then we should also fix
the currently broken error return; those earlier versions of POSIX which
did specify it said that it *may* fail if the requested delay is
1,000,000 microseconds or more, it which case it should set errno to
EINVAL, and return -1; our implementation does not set errno, but
returns EINVAL instead of -1.

Furthermore, if we do vote to keep usleep(), it seems kind of anomalous
that we don't also provide an implementation of sleep(), (which remains
a mandatory POSIX function today).

Thoughts?

--

-- 
Regards,
Keith.

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
(Continue reading)


Gmane