Re: [ANNOUNCEMENT] Test: gnuplot-5.2.3-1

2018-05-07 Thread Tatsuro MATSUOKA 
- Original Message -

> From: Achim Gratz 
> To: cygwin
> Cc: 
> Date: 2018/5/7, Mon 04:41
> Subject: [ANNOUNCEMENT] Test: gnuplot-5.2.3-1
> 
> 
> Gnuplot version 5.2.3 is available as a test version on Cygwin now.
> 
> Note:
> -
> 
> The configuration has changed to not include "backwards compatibility)
> any longer, which removes partial support for deprecated features.
> Unless I hear of problems with this change, this version will be
> promoted to be the current version in a few weeks, so please test your
> scripts with the new version.
> 
> 
> -- 
>               *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
> 
> If you want to unsubscribe from the cygwin-announce mailing list, look
> at the "List-Unsubscribe: " tag in the email header of this message.
> Send email to the address specified there. It will be in the format:
> 
> cygwin-announce-unsubscribe-you=yourdomain@cygwin.com
> 
> If you need more information on unsubscribing, start reading here:
> 
> http://sourceware.org/lists.html#unsubscribe-simple
> 
> Please read *all* of the information on unsubscribing that is available
> starting at this URL.



This is feature request and I do not want the below to implement on 5.2.3 but 
in the future version.

1. wxt support
x11 is obsolated terminal. 
To implement qt terminal, a patch to qt described shown
in my site [1] is required. 
But wxt terminal can be implemented if you link wxwidegets libraries on cygwin.
(One patch required for gnuplot side and require Set NO_AT_BRIDGE environmental 
variable to 1  [1]).

2. cerf support
libcerf is not supported in gnuplot of cygwin official. 
For static library for libcerf it is easy to build but dynamic libraries cannot 
be build by default.
But please consider to implement of complex error function facility.

[1] http://www.tatsuromatsuoka.com/gnuplot/Eng/cygbin/README_TM.txt

Tatsuro


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

[ANNOUNCEMENT] mesa 18.0.3-1

2018-05-07 Thread Yaakov Selkowitz 
The following packages have been uploaded to the Cygwin distribution:

* dri-drivers-18.0.3-1
* libglapi0-18.0.3-1
* libGL1-18.0.3-1
* libGL-devel-18.0.3-1
* libOSMesa8-18.0.3-1
* libOSMesa-devel-18.0.3-1
* libEGL1-18.0.3-1
* libEGL-devel-18.0.3-1
* libGLESv2_2-18.0.3-1
* libGLESv2-devel-18.0.3-1
* windowsdriproto-18.0.3-1

Mesa is an open-source implementation of the OpenGL, OpenGL ES, and EGL 
specifications for rendering interactive 3D graphics.

Complete documentation on OpenGL usage and configuration can be found here:

http://x.cygwin.com/docs/ug/using-glx.html

This is an update to the latest upstream release:

https://www.mesa3d.org/relnotes/18.0.2.html
https://www.mesa3d.org/relnotes/18.0.3.html

--
Yaakov

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

[ANNOUNCEMENT] TeX Live 2018

2018-05-07 Thread Yaakov Selkowitz 
On 2018-05-06 16:57, Ken Brown wrote:
> On 5/6/2018 4:02 PM, Ken Brown wrote:
>> On 4/29/2018 6:16 PM, Yaakov Selkowitz wrote:
>>> On 2018-04-29 08:33, Marco Atzeri wrote:
 On 4/29/2018 11:25 AM, Lemures Lemniscati wrote:
> On each systems, there appeared a dialog telling something like that:
>
>     The procedure entry point 'glBegin' could not be located in the
>     dynamic link library 'cygOSMesa-8.dll'

 I would say that libOSMesa8 had a modification in the list of
 exported symbols in the last version.


 [TXT]    libOSMesa8-17.3.5-1    21-Feb-2018 09:50 267
 [TXT]    libOSMesa8-17.3.8-1    05-Apr-2018 12:44 267
 [TXT]    libOSMesa8-18.0.1-1    23-Apr-2018 07:35 267

 I do not see  glBegin in the last cygOSMesa-8.dll of 18.0.1-1
 So it seems there is an issue on the last libOSMesa8 package
>>>
>>> Indeed, investigating now.
>>
>> I don't know where your are in your investigation, but I think I found
>> the problem.  The attached patch to the mesa sources seems to fix it

That's pretty much what I had locally as well.

> BTW, although the patch suffices to solve the immediate problem, I
> suspect that there may still be a lot of symbols in the various mesa
> DLLs that are exported in the autotools build but not in the meson
> build.  Indeed, there are quite a few 'noinst' libraries in Makefile.am
> files that are not listed in 'link_full' in the meson.build files.  If
> I'm not mistaken, such libraries will be linked with the --whole-archive
> option in the autotools build but not in the meson build.

This took a little more time to understand.  Libtool always treats
convenience libs (iow static noinst_LTLIBRARIES) along the lines of
meson's 'link_full', which results in all of their symbols to be
exported into the shared library into which they are linked (unless
dllexport or .def file are used, of course).  Meson distinguishes
between link_full and link_with, the latter of which is a normal link,
meaning that only those parts referenced elsewhere get pulled in.

With the above fix for OSMesa, a comparison of all the link libraries
between the last 17.3 libtool-based build and the 18.0 meson-based build
shows a lot of internal symbols no longer exported but the public ABI
looks sane now.  osdemo works with today's 18.0.3, so hopefully we are
set, but if there are other issues, please do let me know.

-- 
Yaakov

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

RE: License question (Distribution of cygwin1.dll

2018-05-07 Thread Buchbinder, Barry (NIH/NIAID) [E] 
patrick schmidt sent the following at Monday, May 07, 2018 10:28 AM
>
>I want to use iPerf3.exe in an commercial projekt. iPerf uses the MIT
>License but needs cygwin1.dll in order to function correctly.
>
>I need to distribute iperf3.exe in our commercial software, but we cant
>release the source code of this product. We do not modify cygwin1.dll,
>just distribute and the iPerf3.exe is only called as an seperate
>process.
>
>Does cygwin license allow this and if not is there anyone you can
>contact for other licensing options which do not force you to give out
>the source code?

See page and LGPL links:  https://cygwin.com/licensing.html
FAQ: https://cygwin.com/faq.html#faq.using.bundling-cygwin

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

License question (Distribution of cygwin1.dll

2018-05-07 Thread patrick schmidt 
Hello dear Cygwin community,

I want to use iPerf3.exe in an commercial projekt. iPerf uses the MIT
License but needs cygwin1.dll in order to function correctly.

I need to distribute iperf3.exe in our commercial software, but we cant
release the source code of this product. We do not modify cygwin1.dll, just
distribute and the iPerf3.exe is only called as an seperate process.

Does cygwin license allow this and if not is there anyone you can contact
for other licensing options which do not force you to give out the source
code?

Thank you in advance!

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Sudo for cygwin

2018-05-07 Thread Christian Fersch 

Hi,

Since I was unhappy about the lack of a sudo command in cygwin, I wrote 
a litte
script to emulate it. You can find at 
https://github.com/Chronial/cygwin-sudo.


It runs commands in elevated mode and has pty-passthrough, so you can 
use it in

pipes and run interactive commands like vim through it.

Just wanted to share this, in case it might be useful for anybody else.

Regards,
Christian


--

djangsters UG (haftungsbeschränkt)
Pappelallee 24
D-10437 Berlin



www.djangsters.de 


Geschäftsführer: Sebastian 
Rode



Sitz der Gesellschaft: D-10437 Berlin
Registergericht Berlin, HRB 
150279

USt-IdNr: DE289238324

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] Updated: gcc-7.3.0-2 (x86/x86_64)(Test)

2018-05-07 Thread JonY 
On 05/06/2018 11:54 PM, Ross Smith wrote:
> 
> I've updated gcc-core, gcc-g++, and libstdc++ to 7.3.0-2,
> but the filesystem library still doesn't seem to be working:
> 
> #include 
> #include 
> using namespace std::experimental;
> int main() {
>     filesystem::path p("expfs.cpp");
>     std::cout << p.string() << " " << filesystem::exists(p) << "\n";
> }

Try add -lstdc++fs?



signature.asc
Description: OpenPGP digital signature

re:confirm the design draft of A4 paper

2018-05-07 Thread mandy 
Dear Sir,

It's a nice day!

We are a company mainly in export paper products. We have been in this field 
for many years.

Our paper products contains copy paper, newsprint paper, offset paper, NCR 
paper etc.

Should any of the item be of interest to you, please let me know. We shall be 
glad to give you our the most favorable price upon receipt of your detailed 
requirements.

May be now you have regular partner. If So, please leave my message in your 
email box, maybe someday it will be useful.

Best Wishes! Enjoy your work!
Regards

Mandy