OK, since this isn't the standard release, and the bug is clearly in MinGW
itself, I'll leave it up to users to deal with it, unless you want to submit
a patch (and it is simple and non-intrusive).

On Mon, Jan 4, 2010 at 10:40 PM, lucas_ro <florin...@gmail.com> wrote:

> Ok, I try to make the stuffs more clear.
>
> In order to get the official MinGW 4.4.0 (aka gcc 4.4.0) you have to
> follow the link http://sourceforge.net/projects/mingw/files/. Downward
> that page please look for GCC Version 4 then expand it and find out
> CurrentRelease_gcc-4.4.0. Under the latter branch you may find the
> official release of gcc 4.4.0 for Windows. Please read the content of
> the file gcc-4.4.0-mingw-notes.txt in order to have some hints on the
> installation of this software package.
>
> If you find the above procedure too complicated (and indeed it is)
> then the simplest way to have MinGW-4.4.0 is to download the following
> file: ftp://ftp.qt.nokia.com/misc/MinGW-gcc440_1.zip . It is the
> official release patched in order to allow the building of the
> DirectShow under MinGW.
>
> The executable MinGW 5.1.6 installs the version 3.4.5 of gcc !!!
>
> On Jan 5, 4:38 am, Kenton Varda <ken...@google.com> wrote:
> > OK, I'm pretty confused now.  Apparently there is a MinGW 5.1.6.
>  However,
> > the MinGW version number does not appear to be related to the GCC version
> > number -- it comes with gcc 3.4.5.  Your link talks about building with
> > MinGW and *GCC* 4.4.0.  Last I knew, MinGW had not yet provided an
> official
> > release with GCC 4.x and AFAICT this is still the case.
> >
> > During the install I chose the "current" release.  Maybe you chose the
> > "candidate"?
> >
> >
> >
> > On Mon, Jan 4, 2010 at 12:02 PM, lucas_ro <florin...@gmail.com> wrote:
> > > It's the official stable release. As I observed by searching the web
> > > for a solution the issue regarding 'libstdc++.dll.a' is well known.
> > > Unfortunately it seems that they (mingw team) react very slowly in
> > > fixing the signaled issues/bugs.
> >
> > > The link that helped me is
> > >http://eschew.wordpress.com/2009/09/20/building-protobuf-with-mingw-g.
> ..
> > > .
> > > (however it is not necessary to install the mozilla-build tree).
> >
> > > On Jan 4, 9:27 pm, Kenton Varda <ken...@google.com> wrote:
> > > > I see.  Is mingw-4.4.0 a stable release or a beta?  Unfortunately
> their
> > > web
> > > > site is pretty terribly designed and I cannot figure this out.  If
> it's
> > > an
> > > > official release then we should probably work around the bug, but
> > > otherwise
> > > > I assume they'll fix it since it's a known issue.
> >
> > > > On Mon, Jan 4, 2010 at 11:07 AM, lucas_ro <florin...@gmail.com>
> wrote:
> > > > > Eventually I succeeded by changing in the file  libstdc++.la the
> value
> > > > > of the variable library_names from 'libstdc++.dll.a' to
> 'libstdc++.a'.
> > > > > The libtool was complaining about the missing of the file 'libstdc+
> > > > > +.dll.a'. It seems that this is a mingw-4.4.0 known issue.
> >
> > > > > Also I choose to build only the static library (passing the option
> --
> > > > > disable-shared on to the command 'configure').
> >
> > > > > On Jan 4, 8:07 pm, Kenton Varda <ken...@google.com> wrote:
> > > > > > Did you try and fail?  If so, please post the error log.
> >
> > > > > > On Mon, Jan 4, 2010 at 5:52 AM, lucas_ro <florin...@gmail.com>
> > > wrote:
> > > > > > > Hello,
> >
> > > > > > > Have anyone succeeded to build the protocol buffers using
> > > MinGW-4.4.0
> > > > > > > under Windows ?
> >
> > > > > > > Thank you,
> > > > > > > Florin
> >
> > > > > > > --
> >
> > > > > > > You received this message because you are subscribed to the
> Google
> > > > > Groups
> > > > > > > "Protocol Buffers" group.
> > > > > > > To post to this group, send email to protobuf@googlegroups.com
> .
> > > > > > > To unsubscribe from this group, send email to
> > > > > > > protobuf+unsubscr...@googlegroups.com<protobuf%2bunsubscr...@googlegroups.com>
> <protobuf%2bunsubscr...@googlegroups.c om>
> > > <protobuf%2bunsubscr...@googlegroups.c om>
> > > > > <protobuf%2bunsubscr...@googlegroups.c om>
> > > > > > > .
> > > > > > > For more options, visit this group at
> > > > > > >http://groups.google.com/group/protobuf?hl=en.
> >
> > > > > --
> >
> > > > > You received this message because you are subscribed to the Google
> > > Groups
> > > > > "Protocol Buffers" group.
> > > > > To post to this group, send email to proto...@googlegroups.com.
> > > > > To unsubscribe from this group, send email to
> > > > > protobuf+unsubscr...@googlegroups.com<protobuf%2bunsubscr...@googlegroups.com>
> <protobuf%2bunsubscr...@googlegroups.c om>
> > > <protobuf%2bunsubscr...@googlegroups.c om>
> > > > > .
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/protobuf?hl=en.
> >
> > > --
> >
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Protocol Buffers" group.
> > > To post to this group, send email to proto...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > protobuf+unsubscr...@googlegroups.com<protobuf%2bunsubscr...@googlegroups.com>
> <protobuf%2bunsubscr...@googlegroups.c om>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/protobuf?hl=en.
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to proto...@googlegroups.com.
> To unsubscribe from this group, send email to
> protobuf+unsubscr...@googlegroups.com<protobuf%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/protobuf?hl=en.
>
>
>
--
You received this message because you are subscribed to the Google Groups "Protocol Buffers" group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.

Reply via email to