From: Atsushi S. <sa...@jp...> - 2008-03-28 08:26:07
|
Hi, I have a question about zlib compilation on MSYS. (If this mailing list is wrong, please suggest me.) Is there any latest zlib source code packages for MSYS available? ================== I am trying to create msys-z.dll on MSYS. So I use the code zlib-1.2.3-MSYS-1.0.11-1-src.tar.bz2. I try to execute msys-build-zlib But gcc compier 3.4.5 (mingw special) says error on compilation like. cc1.exe: error: unrecognized command line option "-fnative-struct" `-mcpu=' is deprecated. Use `-mtune' or '-march=' instead. I am wondering removing -fnative-struct is OK or not. =================== Thanks Atsushi SAKAI |
From: JonY <10...@gm...> - 2008-03-28 09:19:03
|
Atsushi SAKAI wrote: > Hi, > > I have a question about zlib compilation on MSYS. > (If this mailing list is wrong, please suggest me.) > > Is there any latest zlib source code packages for MSYS available? > > ================== > I am trying to create msys-z.dll on MSYS. > So I use the code zlib-1.2.3-MSYS-1.0.11-1-src.tar.bz2. > > I try to execute > msys-build-zlib > But gcc compier 3.4.5 (mingw special) says error on compilation > like. > cc1.exe: error: unrecognized command line option "-fnative-struct" > `-mcpu=' is deprecated. Use `-mtune' or '-march=' instead. > > I am wondering removing -fnative-struct is OK or not. > =================== > > Thanks > Atsushi SAKAI > > > > Hi, zlib-1.2.3-MSYS-1.0.11-1-src.tar.bz2, as the name suggests, is for MSYS not for MinGW. What you do want is the mingw version. You can grab the official zlib 1.2.3 source code and it builds fine without any modification. Be sure to run configure first than make. Make sure you use --prefix=/mingw. |
From: Charles W. <cwi...@us...> - 2008-03-28 13:36:08
|
Atsushi SAKAI wrote: > Is there any latest zlib source code packages for MSYS available? Yes. You've already found it. > I am trying to create msys-z.dll on MSYS. > So I use the code zlib-1.2.3-MSYS-1.0.11-1-src.tar.bz2. Are you SURE you want msys-z.dll? This is a zlib library that requires the GPL'ed msys-1.0.dll to operate. Which means that any client code that uses msys-z.dll must be released under the GPL. (and, zlib-1.2.3-MSYS-1.0.11-1.tar.bz2 already provides msys-z.dll). Most people shouldn't concern themselves with MSYS components; they should be regarded as TOOLS useful for building *mingw* (that is, native win32) items. Unless you want to help create those tools. I think it is more likely that you really want a native version of zlib (e.g. libz.dll) as the other correspondent suggested. Google 'zlib mingwPORT'. That having been said, to compile MSYS components, you need several things. First, you have to install the files in the MSYS System Builder Technology Preview: msysDVLPR-1.0.0-alpha-1 release category, including: msysDVLPR-1.0.0-alpha-1.tar.gz and updating with autoconf-2.61-MSYS-1.0.11-1.tar.bz2 automake-1.10-MSYS-1.0.11-1.tar.bz2 libtool1.5-1.5.25a-20070701-MSYS-1.0.11-1.tar.bz2 termcap-20050421-MSYS-1.0.11-1.tar.bz2 Secondly, you have to launch msys.bat with the argument "MSYS". This will set the appropriate environment variables and set your PATH so that the msysDVLPR gcc (a variant of gcc-2.95.3) appears in your PATH before the mingw gcc-3.4.5. THEN the msys-build-zlib script inside zlib-1.2.3-MSYS-1.0.11-1-src.tar.bz2 will work for you. -- Chuck |
From: Tor L. <tm...@ik...> - 2008-03-28 17:33:37
|
> I think it is more likely that you really want a native version of zlib > (e.g. libz.dll) as the other correspondent suggested. Google 'zlib > mingwPORT'. Or just use the official binary (zlib1.dll) conveniently provided at www.zlib.net? I don't understand why one would desperately need to rebuilt zlib oneself, when there is a perfectly nice pre-built binary available? But then I am a lazy bastard... (Unless one wants to enhance it and/or need to debug it, etc.) --tml |
From: Roumen P. <bug...@ro...> - 2008-03-28 18:18:51
|
Tor Lillqvist wrote: >> I think it is more likely that you really want a native version of zlib >> (e.g. libz.dll) as the other correspondent suggested. Google 'zlib >> mingwPORT'. > > Or just use the official binary (zlib1.dll) conveniently provided at > www.zlib.net? > > I don't understand why one would desperately need to rebuilt zlib > oneself, when there is a perfectly nice pre-built binary available? > But then I am a lazy bastard... (Unless one wants to enhance it and/or > need to debug it, etc.) > > --tml Usually no, but if you application crash due different versions of C-runtime ... Roumen |
From: Atsushi S. <sa...@jp...> - 2008-03-31 07:27:24
|
Thanks for various comments. Now I understands the msys-*.dll license and needs. I erase the msys-*.dll related files for my build environment. With replacing msys-z.dll to static zlib, My problem is solved. c.f. I am still debugging gtk-vnc in my spare time. Thanks Atsushi SAKAI "Tor Lillqvist" <tm...@ik...> wrote: > > > > > I think it is more likely that you really want a native version of zlib > > (e.g. libz.dll) as the other correspondent suggested. Google 'zlib > > mingwPORT'. > > Or just use the official binary (zlib1.dll) conveniently provided at > www.zlib.net? > > I don't understand why one would desperately need to rebuilt zlib > oneself, when there is a perfectly nice pre-built binary available? > But then I am a lazy bastard... (Unless one wants to enhance it and/or > need to debug it, etc.) > > --tml > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users |
From: ephraim t. <aa...@go...> - 2009-05-20 10:15:10
|
Charles Wilson <cwilso11@...> writes: > > > Atsushi SAKAI wrote: > > Is there any latest zlib source code packages for MSYS available? > > Yes. You've already found it. > > > I am trying to create msys-z.dll on MSYS. > > So I use the code zlib-1.2.3-MSYS-1.0.11-1-src.tar.bz2. > > Are you SURE you want msys-z.dll? This is a zlib library that requires > the GPL'ed msys-1.0.dll to operate. Which means that any client code > that uses msys-z.dll must be released under the GPL. > > (and, zlib-1.2.3-MSYS-1.0.11-1.tar.bz2 already provides msys-z.dll). > > Most people shouldn't concern themselves with MSYS components; they > should be regarded as TOOLS useful for building *mingw* (that is, native > win32) items. Unless you want to help create those tools. > > I think it is more likely that you really want a native version of zlib > (e.g. libz.dll) as the other correspondent suggested. Google 'zlib > mingwPORT'. > > That having been said, to compile MSYS components, you need several > things. First, you have to install the files in the > > MSYS System Builder > Technology Preview: msysDVLPR-1.0.0-alpha-1 release > category, including: > > msysDVLPR-1.0.0-alpha-1.tar.gz > > and updating with > autoconf-2.61-MSYS-1.0.11-1.tar.bz2 > automake-1.10-MSYS-1.0.11-1.tar.bz2 > libtool1.5-1.5.25a-20070701-MSYS-1.0.11-1.tar.bz2 > termcap-20050421-MSYS-1.0.11-1.tar.bz2 > > Secondly, you have to launch msys.bat with the argument "MSYS". This > will set the appropriate environment variables and set your PATH so that > the msysDVLPR gcc (a variant of gcc-2.95.3) appears in your PATH before > the mingw gcc-3.4.5. > > THEN the msys-build-zlib script inside > zlib-1.2.3-MSYS-1.0.11-1-src.tar.bz2 will work for you. > > -- > Chuck > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > MinGW-users mailing list > MinGW-users@... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > > heads up, chuck #...I found, A bullet with your name on it#, Still On the Run, Bill Miller apologies for reviving the "nearly dead" but i've been trying to confirm my msys developer environment by msys-building zlib, as per your instructions, and as stewie griffin once said, it's gone "not well, brian, not well at all." (i can't do the voice.) see, http://article.gmane.org/gmane.comp.gnu.mingw.user/29737 and http://article.gmane.org/gmane.comp.gnu.mingw.user/29743 (for a non html/mime version, sorry) so far, all that's been suggested is an include problem. but, without trying to insult anyone's intelligence, i'm pretty sure it's a linking problem. and if i had to put money on it, i'd say it was a problem with c/c++ library confusion, which is typically the cause of "undefined reference to"'s. but what do i know? by any chance, do you know of a good source of information on msysdev environment setup? because with all the "install this," "but not in the same root," "except for versions," "then unpack these over," and "bend over, grab your ankles and kiss your ... goodbye" i'm royally confused. |
From: ephraim t. <aa...@go...> - 2009-05-20 10:55:55
|
On Wed, May 20, 2009 at 11:10 AM, ephraim tutt <aa...@go...> wrote: > Charles Wilson <cwilso11@...> writes: > >> >> >> Atsushi SAKAI wrote: >> > Is there any latest zlib source code packages for MSYS available? >> >> Yes. You've already found it. >> >> > I am trying to create msys-z.dll on MSYS. >> > So I use the code zlib-1.2.3-MSYS-1.0.11-1-src.tar.bz2. >> >> Are you SURE you want msys-z.dll? This is a zlib library that requires >> the GPL'ed msys-1.0.dll to operate. Which means that any client code >> that uses msys-z.dll must be released under the GPL. >> >> (and, zlib-1.2.3-MSYS-1.0.11-1.tar.bz2 already provides msys-z.dll). >> >> Most people shouldn't concern themselves with MSYS components; they >> should be regarded as TOOLS useful for building *mingw* (that is, native >> win32) items. Unless you want to help create those tools. >> >> I think it is more likely that you really want a native version of zlib >> (e.g. libz.dll) as the other correspondent suggested. Google 'zlib >> mingwPORT'. >> >> That having been said, to compile MSYS components, you need several >> things. First, you have to install the files in the >> >> MSYS System Builder >> Technology Preview: msysDVLPR-1.0.0-alpha-1 release >> category, including: >> >> msysDVLPR-1.0.0-alpha-1.tar.gz >> >> and updating with >> autoconf-2.61-MSYS-1.0.11-1.tar.bz2 >> automake-1.10-MSYS-1.0.11-1.tar.bz2 >> libtool1.5-1.5.25a-20070701-MSYS-1.0.11-1.tar.bz2 >> termcap-20050421-MSYS-1.0.11-1.tar.bz2 >> >> Secondly, you have to launch msys.bat with the argument "MSYS". This >> will set the appropriate environment variables and set your PATH so that >> the msysDVLPR gcc (a variant of gcc-2.95.3) appears in your PATH before >> the mingw gcc-3.4.5. >> >> THEN the msys-build-zlib script inside >> zlib-1.2.3-MSYS-1.0.11-1-src.tar.bz2 will work for you. >> >> -- >> Chuck >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >> _______________________________________________ >> MinGW-users mailing list >> MinGW-users@... >> >> You may change your MinGW Account Options or unsubscribe at: >> https://lists.sourceforge.net/lists/listinfo/mingw-users >> >> > > heads up, chuck > > #...I found, A bullet with your name on it#, Still On the Run, Bill Miller > > apologies for reviving the "nearly dead" but i've been trying to confirm my msys > developer environment by msys-building zlib, as per your instructions, and as > stewie griffin once said, it's gone "not well, brian, not well at all." (i > can't do the voice.) > > see, http://article.gmane.org/gmane.comp.gnu.mingw.user/29737 > and http://article.gmane.org/gmane.comp.gnu.mingw.user/29743 (for a non > html/mime version, sorry) > > so far, all that's been suggested is an include problem. but, without trying to > insult anyone's intelligence, i'm pretty sure it's a linking problem. and if i > had to put money on it, i'd say it was a problem with c/c++ library confusion, > which is typically the cause of "undefined reference to"'s. but what do i know? > > by any chance, do you know of a good source of information on msysdev > environment setup? because with all the "install this," "but not in the same > root," "except for versions," "then unpack these over," and "bend over, grab > your ankles and kiss your ... goodbye" i'm royally confused. > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. > > Most annoying abuses are: > 1) Top posting > 2) Thread hijacking > 3) HTML/MIME encoded mail > 4) Improper quoting > 5) Improper trimming > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > i stand corrected:( |
From: JonY <10...@gm...> - 2009-05-20 11:09:57
|
On 5/20/2009 18:10, ephraim tutt wrote: > > heads up, chuck > > #...I found, A bullet with your name on it#, Still On the Run, Bill Miller > > apologies for reviving the "nearly dead" but i've been trying to confirm my msys > developer environment by msys-building zlib, as per your instructions, and as > stewie griffin once said, it's gone "not well, brian, not well at all." (i > can't do the voice.) > > see, http://article.gmane.org/gmane.comp.gnu.mingw.user/29737 > and http://article.gmane.org/gmane.comp.gnu.mingw.user/29743 (for a non > html/mime version, sorry) > > so far, all that's been suggested is an include problem. but, without trying to > insult anyone's intelligence, i'm pretty sure it's a linking problem. and if i > had to put money on it, i'd say it was a problem with c/c++ library confusion, > which is typically the cause of "undefined reference to"'s. but what do i know? > To be fair, its a bit of both. Read <sys/errno.h> and you'll understand it. > by any chance, do you know of a good source of information on msysdev > environment setup? because with all the "install this," "but not in the same > root," "except for versions," "then unpack these over," and "bend over, grab > your ankles and kiss your ... goodbye" i'm royally confused. > > Its an old fork of Cygwin-1.3. It would help if you elaborated on what are you confused about. |
From: Charles W. <cwi...@us...> - 2009-05-20 12:53:26
|
ephraim tutt wrote: > apologies for reviving the "nearly dead" but i've been trying to confirm my msys > developer environment by msys-building zlib, as per your instructions, and as > stewie griffin once said, it's gone "not well, brian, not well at all." (i > can't do the voice.) > > see, http://article.gmane.org/gmane.comp.gnu.mingw.user/29737 > and http://article.gmane.org/gmane.comp.gnu.mingw.user/29743 (for a non > html/mime version, sorry) > > so far, all that's been suggested is an include problem. but, without trying to > insult anyone's intelligence, i'm pretty sure it's a linking problem. and if i > had to put money on it, i'd say it was a problem with c/c++ library confusion, > which is typically the cause of "undefined reference to"'s. but what do i know? > > by any chance, do you know of a good source of information on msysdev > environment setup? because with all the "install this," "but not in the same > root," "except for versions," "then unpack these over," and "bend over, grab > your ankles and kiss your ... goodbye" i'm royally confused. I've been following the thread, but Real Life has been kicking my @ss lately. I won't have time to look in to this -- and several other MinGW/MSYS issues -- until this weekend. sorry... -- Chuck |