I don't think anyone here is likely to have any idea what the problem is. I
cannot reproduce it, so I can't be of any help. You'll need to debug it
yourself. Try examining the build logs to see exactly how your compiler is
being invoked and figure out how it is *supposed* to be invoked to get the
results you want. Maybe if you post those, we might be able to figure out
how to invoke "configure" to get what you want.
On Mon, Feb 1, 2010 at 1:13 PM, SyRenity <stas.os...@gmail.com> wrote:
> Any idea of the issue below?
> I'm currently using static libraries compiled on another (virtual) 32-
> bit machine, which seems to be working fine, but I really would prefer
> a native solution.
> On Jan 29, 11:28 pm, Stas Oskin <stas.os...@gmail.com> wrote:
> > Sorry, forwarding to list as well.
> > ---------- Forwarded message ----------
> > From: Stas Oskin <stas.os...@gmail.com>
> > Date: Fri, Jan 29, 2010 at 11:27 PM
> > Subject: Re: [protobuf] Re: Cross-compiling protobuf to 32-bit
> > To: Kenton Varda <ken...@google.com>
> > Hi.
> > > And when you configure other autotool-based packages the same way, it
> > > works?
> > Yes, it is.
> > > You said you were using the -m32 flag. Where is it?
> > It actually broke the compilation, and didn't let it finish.
> > Is there any one using a correct cross-architecture compile on RedHat?
> > Regards.
> 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
> For more options, visit this group at
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
For more options, visit this group at