From: Earnie B. <ea...@us...> - 2013-02-21 04:10:27
|
On Wed, Feb 20, 2013 at 7:56 AM, Earnie Boyd wrote: > On Wed, Feb 20, 2013 at 5:42 AM, Алексей Павлов wrote: >> Hi! >> Can you upload attached programs to msys packages on sourceforge? They >> builded with msys-gcc. > > Alex, > > I can give you the ability to do that but we need to discuss it on the > mingw-dvlpr list first. You also need to udpate the mingw-get .xml > files for this. You can get those from mingw-dist repository[1]. You > should search the mingw-dvlpr repository for discussions of mingw-get. > > [1] https://sourceforge.net/p/mingw/mingw-dist/ci/73a7b8ae66d9d5fe1a8a287b9= > 72d2afc8a192626/tree/ Alexey, sorry, I meant to add mingw-dlvlpr to the reply earlier today. Erwin, can you please work with Alexey to get this completed? He already has the packages broken in to the various bits. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Erwin W. <wat...@xs...> - 2013-02-21 21:14:25
|
Earnie Boyd schreef, Op 21-2-2013 5:10: > On Wed, Feb 20, 2013 at 7:56 AM, Earnie Boyd wrote: >> On Wed, Feb 20, 2013 at 5:42 AM, Алексей Павлов wrote: >>> Hi! >>> Can you upload attached programs to msys packages on sourceforge? They >>> builded with msys-gcc. >> Alex, >> >> I can give you the ability to do that but we need to discuss it on the >> mingw-dvlpr list first. You also need to udpate the mingw-get .xml >> files for this. You can get those from mingw-dist repository[1]. You >> should search the mingw-dvlpr repository for discussions of mingw-get. >> >> [1] https://sourceforge.net/p/mingw/mingw-dist/ci/73a7b8ae66d9d5fe1a8a287b9= >> 72d2afc8a192626/tree/ > Alexey, sorry, I meant to add mingw-dlvlpr to the reply earlier today. > Erwin, can you please work with Alexey to get this completed? He > already has the packages broken in to the various bits. > Hi, I started with m4. I want to take the opportunity to replace old packaging script with new mgwport scripts. Now I have a nasty problem with configure. See mingw list. Can one of you replay what I did with mgwport? Alexey's package with the old packaging script gives me the same problem. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Earnie B. <ea...@us...> - 2013-02-21 21:51:11
|
On Thu, Feb 21, 2013 at 4:14 PM, Erwin Waterlander wrote: > Earnie Boyd schreef, Op 21-2-2013 5:10: >> On Wed, Feb 20, 2013 at 7:56 AM, Earnie Boyd wrote: >>> On Wed, Feb 20, 2013 at 5:42 AM, Алексей Павлов wrote: >>>> Hi! >>>> Can you upload attached programs to msys packages on sourceforge? They >>>> builded with msys-gcc. >>> Alex, >>> >>> I can give you the ability to do that but we need to discuss it on the >>> mingw-dvlpr list first. You also need to udpate the mingw-get .xml >>> files for this. You can get those from mingw-dist repository[1]. You >>> should search the mingw-dvlpr repository for discussions of mingw-get. >>> >>> [1] https://sourceforge.net/p/mingw/mingw-dist/ci/73a7b8ae66d9d5fe1a8a287b9= >>> 72d2afc8a192626/tree/ >> Alexey, sorry, I meant to add mingw-dlvlpr to the reply earlier today. >> Erwin, can you please work with Alexey to get this completed? He >> already has the packages broken in to the various bits. >> > > Hi, > > I started with m4. I want to take the opportunity to replace old > packaging script with new mgwport scripts. > Now I have a nasty problem with configure. See mingw list. > Can one of you replay what I did with mgwport? > Alexey's package with the old packaging script gives me the same problem. I don't have an answer. Maybe, something in your environment, BLODA like. I can give the configure a try tomorrow. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Erwin W. <wat...@xs...> - 2013-02-21 23:07:20
|
Earnie Boyd schreef, Op 21-2-2013 22:51: > On Thu, Feb 21, 2013 at 4:14 PM, Erwin Waterlander wrote: > >> Hi, >> >> I started with m4. I want to take the opportunity to replace old >> packaging script with new mgwport scripts. >> Now I have a nasty problem with configure. See mingw list. >> Can one of you replay what I did with mgwport? >> Alexey's package with the old packaging script gives me the same problem. > I don't have an answer. Maybe, something in your environment, BLODA > like. I can give the configure a try tomorrow. > Not needed any more. Greg Chicares solved the problem. See mingw list. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2013-02-22 11:59:38
|
Op 21-2-2013 22:14, Erwin Waterlander schreef: > Earnie Boyd schreef, Op 21-2-2013 5:10: >> On Wed, Feb 20, 2013 at 7:56 AM, Earnie Boyd wrote: >>> On Wed, Feb 20, 2013 at 5:42 AM, Алексей Павлов wrote: >>>> Hi! >>>> Can you upload attached programs to msys packages on sourceforge? They >>>> builded with msys-gcc. >>> Alex, >>> >>> I can give you the ability to do that but we need to discuss it on the >>> mingw-dvlpr list first. You also need to udpate the mingw-get .xml >>> files for this. You can get those from mingw-dist repository[1]. You >>> should search the mingw-dvlpr repository for discussions of mingw-get. >>> >>> [1] https://sourceforge.net/p/mingw/mingw-dist/ci/73a7b8ae66d9d5fe1a8a287b9= >>> 72d2afc8a192626/tree/ >> Alexey, sorry, I meant to add mingw-dlvlpr to the reply earlier today. >> Erwin, can you please work with Alexey to get this completed? He >> already has the packages broken in to the various bits. >> > Hi, > > I started with m4. I want to take the opportunity to replace old > packaging script with new mgwport scripts. > Now I have a nasty problem with configure. See mingw list. > Can one of you replay what I did with mgwport? > Alexey's package with the old packaging script gives me the same problem. > > regards, > Hi, I have m4 packages ready. Built with mgwport. See http://waterlan.home.xs4all.nl/msys/m4/ When there are no objections, I'm going upload these in the weekend. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2013-02-22 21:50:33
|
Erwin Waterlander schreef, Op 22-2-2013 12:59: > Hi, > > I have m4 packages ready. Built with mgwport. > See http://waterlan.home.xs4all.nl/msys/m4/ > When there are no objections, I'm going upload these in the weekend. > > regards, > I put new files at http://waterlan.home.xs4all.nl/msys/m4/, and bumped the version to 1.4.16-2. I forced the strstr linear time test to 'no'. Thanks to Keith. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2013-02-22 22:13:24
|
Earnie Boyd schreef, Op 21-2-2013 5:10: > On Wed, Feb 20, 2013 at 7:56 AM, Earnie Boyd wrote: >> On Wed, Feb 20, 2013 at 5:42 AM, Алексей Павлов wrote: >>> Hi! >>> Can you upload attached programs to msys packages on sourceforge? They >>> builded with msys-gcc. >> Alex, >> >> I can give you the ability to do that but we need to discuss it on the >> mingw-dvlpr list first. You also need to udpate the mingw-get .xml >> files for this. You can get those from mingw-dist repository[1]. You >> should search the mingw-dvlpr repository for discussions of mingw-get. >> >> [1] https://sourceforge.net/p/mingw/mingw-dist/ci/73a7b8ae66d9d5fe1a8a287b9= >> 72d2afc8a192626/tree/ > Alexey, sorry, I meant to add mingw-dlvlpr to the reply earlier today. > Erwin, can you please work with Alexey to get this completed? He > already has the packages broken in to the various bits. > Hi Alexey, You are welcome to help. If you have packages ready then put them somewhere where we can download them for review. The standard method of packaging is using a mgwport script. Some older packages are not packaged with mgwport yet. Then a new version is a good opportunity to change it to mgwport. Mgwport is derived from cygport, from the Cygwin project, and works about the same. If you install mgwport you can find a manual in \mingw\share\doc\mgwport\0.10.6\README. You can also look at examples of other packages. If you have questions, let us know. best regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Keith M. <kei...@us...> - 2013-02-22 22:28:49
|
On 22/02/13 22:13, Erwin Waterlander wrote: > The standard method of packaging is using a mgwport script. Some older > packages are not packaged with mgwport yet. Then a new version is a good > opportunity to change it to mgwport. It may be Chuck's preferred way, but it isn't mine. I have "voiced" serious reservations here, in the past; I have yet to receive a satisfactory response. I do not like mgwport. I do not like the structure of the packages which Chuck generates with it. I will not use it myself; neither will I require anyone else to do so. It is *not* a project standard. -- Regards, Keith. |
From: Erwin W. <wat...@xs...> - 2013-02-22 22:53:11
|
Keith Marshall schreef, Op 22-2-2013 23:28: > On 22/02/13 22:13, Erwin Waterlander wrote: >> The standard method of packaging is using a mgwport script. Some older >> packages are not packaged with mgwport yet. Then a new version is a good >> opportunity to change it to mgwport. > It may be Chuck's preferred way, but it isn't mine. I have "voiced" > serious reservations here, in the past; I have yet to receive a > satisfactory response. > > I do not like mgwport. I do not like the structure of the packages > which Chuck generates with it. I will not use it myself; neither will I > require anyone else to do so. It is *not* a project standard. > Oh, sorry. I was under the impression that mgwport was standard. Or at least that the old scripts were passé. I like mgwport, but it is not holy for me. I can also live with an alternative solution. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Earnie B. <ea...@us...> - 2013-02-23 00:51:19
|
On Fri, Feb 22, 2013 at 5:53 PM, Erwin Waterlander wrote: > Keith Marshall schreef, Op 22-2-2013 23:28: >> On 22/02/13 22:13, Erwin Waterlander wrote: >>> The standard method of packaging is using a mgwport script. Some older >>> packages are not packaged with mgwport yet. Then a new version is a good >>> opportunity to change it to mgwport. >> It may be Chuck's preferred way, but it isn't mine. I have "voiced" >> serious reservations here, in the past; I have yet to receive a >> satisfactory response. >> >> I do not like mgwport. I do not like the structure of the packages >> which Chuck generates with it. I will not use it myself; neither will I >> require anyone else to do so. It is *not* a project standard. >> > > Oh, sorry. I was under the impression that mgwport was standard. Or at > least that the old scripts were passé. I like mgwport, but it is not > holy for me. I can also live with an alternative solution. It's more of, its a preferred method by a package maintainer, if that method works for you too, then use it. If it doesn't use a different method. The point is the method should be able to create the packages we deliver. For mingw-org-wsl I wrote targets in Makefile.in to handle the packaging. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Erwin W. <wat...@xs...> - 2013-02-24 17:00:13
|
Op 23-2-2013 20:54, Alexey Pavlov schreef: > This is links to my updates: > > Autoconf: > https://www.dropbox.com/s/97qfyslaxtnk2zd/autoconf-2.69-1-msys-1.0.17-bin.tar.lzma > https://www.dropbox.com/s/u91061ofhkesfhq/autoconf-2.69-1-msys-1.0.17-doc.tar.lzma > https://www.dropbox.com/s/z9s18l4bxd4c5nz/autoconf-2.69-1-msys-1.0.17-lic.tar.lzma > https://www.dropbox.com/s/3v1e0wgrkzs4wyo/autoconf-2.69-1-msys-1.0.17-src.tar.lzma > > Automake: > https://www.dropbox.com/s/zdwknqg4xw05zhw/automake-1.12.6-1-msys-1.0.18-bin.tar.lzma > https://www.dropbox.com/s/1m2qhzfwtiq91zo/automake-1.12.6-1-msys-1.0.18-doc.tar.lzma > https://www.dropbox.com/s/xq0besj4nxi80yx/automake-1.12.6-1-msys-1.0.18-lic.tar.lzma > https://www.dropbox.com/s/pqtsb6y5zm5c269/automake-1.12.6-1-msys-1.0.18-src.tar.lzma > > Libtool: > https://www.dropbox.com/s/tjprro3laj51arb/libltdl-2.4.2-1-msys-1.0.17-dev.tar.lzma > https://www.dropbox.com/s/3thmr29ouj4z20j/libltdl-2.4.2-1-msys-1.0.17-dll-7.tar.lzma > https://www.dropbox.com/s/nre2omfuoiptkh5/libtool-2.4.2-1-msys-1.0.17-bin.tar.lzma > https://www.dropbox.com/s/tvcbfotm6x0uy2k/libtool-2.4.2-1-msys-1.0.17-doc.tar.lzma > https://www.dropbox.com/s/pak6cc4xygwtxr0/libtool-2.4.2-1-msys-1.0.17-lic.tar.lzma > https://www.dropbox.com/s/o0tu2o4kh3o7zrz/libtool-2.4.2-1-msys-1.0.17-src.tar.lzma > > I didn't have time to port scripts to mgwport if it not because I spend all my free time to port recent Cygwin to new MSYS2. > > Hi Alexey, Thanks a lot. I have also limited time. Let's do them one by one. First autoconf. Autoconf is already using mgwport, so you don't need to work on that. I noticed you didn't update the msys README file, the README file that is put under MSYS-PATCHES. You did not update the patch files. They still succeeded, with an offset, but I always update the patch files to the latest source. I don't know if there is an official policy on this topic... What you can do is run until preparation: mgwport autoconf-2.69-1.msysport prep And then you can go into the autoconf-2.69-1/ directory and run diff on the origsrc/ and src/ directories to create new patch files. If you first update the README file then you have that covered too. I ran this diff command for m4: diff -r -c -N --exclude=*.orig origsrc src > ../m4.patch Because you have published autoconf-2.69-1 on the internet, and you are going to make changes, your next version has to be autoconf-2.69-2. Because you never know who downloaded the files already. best regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: waterlan <wat...@xs...> - 2013-02-25 08:34:33
|
Alexey Pavlov schreef op 2013-02-23 20:54: > > I didn't have time to port scripts to mgwport if it not because I > spend all my free time to port recent Cygwin to new MSYS2. > Hi, Are you working with Earnie on this? -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Alexey P. <ale...@gm...> - 2013-02-25 08:46:37
|
Earnie consult me if I have any question. But now only I work on this. If you have time you can help I think. There is repository for msys2 code http://sourceforge.net/p/mingw/msys2-runtime/ci/0b9cb33ece2a3a5b26e84adf502ea017560703d7/tree. Now I have crosscompilers (4.5.3 & 4.7.2) from Cygwin to Msys2. I can build many tools but now msys2.dll do not contain msys functionality, this is cygwin.dll with some cosmetic changes. When I got small environment where I can build native msys2 apps I try to add all necessary changes. Best regards. 25.02.2013, в 12:33, waterlan <wat...@xs...> написал(а): > Alexey Pavlov schreef op 2013-02-23 20:54: > >> >> I didn't have time to port scripts to mgwport if it not because I >> spend all my free time to port recent Cygwin to new MSYS2. >> > > Hi, > > Are you working with Earnie on this? > > -- > Erwin Waterlander > http://waterlan.home.xs4all.nl/ > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
From: waterlan <wat...@xs...> - 2013-02-25 12:52:02
|
Alexey Pavlov schreef op 2013-02-25 09:45: > Earnie consult me if I have any question. But now only I work on > this. If you have time you can help I think. > There is repository for msys2 code > http://sourceforge.net/p/mingw/msys2-runtime/ci/0b9cb33ece2a3a5b26e84adf502ea017560703d7/tree. > Now I have crosscompilers (4.5.3 & 4.7.2) from Cygwin to Msys2. I can > build many tools but now msys2.dll do not contain msys functionality, > this is cygwin.dll with some cosmetic changes. When I got small > environment where I can build native msys2 apps I try to add all > necessary changes. > Hi Alexey, OK. Thanks for the info. By the way, you should not "top-post" when you reply to the mingw lists. See the MinGW etiquette rules at http://www.mingw.org/lists.shtml Some people will start to ignore you if you keep on top-posting. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Alexey P. <ale...@gm...> - 2013-02-25 19:56:04
|
I create simple MSYS2 environment. It now act as Cygwin but I think now we can build msys.dll and debug in this environment. Environment is builded from cygwin-msys2 crosscompiler. It contains gcc-4.5.3. Also I have gcc-4.7.2 but msys.dll seems not work with this gcc. If anyone is interesting in working of msys2 porting I post link to this environment: https://www.dropbox.com/s/lixw3u3b2cf3qpp/msys2-4.5.3-simple.7z |
From: Earnie B. <ea...@us...> - 2013-02-25 13:04:45
|
On Sun, Feb 24, 2013 at 11:59 AM, Erwin Waterlander <wat...@xs...> wrote: > You did not update the patch files. They still succeeded, with an > offset, but I always update the patch files to the latest source. I > don't know if there is an official policy on this topic... Yes, the patches should be refreshed to match the version being distributed. Otherwise you'll get senseless noise on the users list. -- Earnie -- https://sites.google.com/site/earnieboyd |
From: Erwin W. <wat...@xs...> - 2013-02-27 14:05:22
|
Op 25-2-2013 14:04, Earnie Boyd schreef: > On Sun, Feb 24, 2013 at 11:59 AM, Erwin Waterlander <wat...@xs...> wrote: >> You did not update the patch files. They still succeeded, with an >> offset, but I always update the patch files to the latest source. I >> don't know if there is an official policy on this topic... > Yes, the patches should be refreshed to match the version being > distributed. Otherwise you'll get senseless noise on the users list. > Hi Alexey, If you don't have time, and want to concentrate on MSYS2, then I can repackage autoconf with updated patch files and release notes. OK? -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Алексей П. <al...@gm...> - 2013-02-27 15:27:08
|
2013/2/27 Erwin Waterlander <wat...@xs...>: > Op 25-2-2013 14:04, Earnie Boyd schreef: >> On Sun, Feb 24, 2013 at 11:59 AM, Erwin Waterlander <wat...@xs...> wrote: >>> You did not update the patch files. They still succeeded, with an >>> offset, but I always update the patch files to the latest source. I >>> don't know if there is an official policy on this topic... >> Yes, the patches should be refreshed to match the version being >> distributed. Otherwise you'll get senseless noise on the users list. >> > > Hi Alexey, > > If you don't have time, and want to concentrate on MSYS2, then I can > repackage autoconf with updated patch files and release notes. > OK? Yes you can do it! I have no time for it. MSYS2 is in progress) Also I have issues with my Qt-builds project. I need do more work. |