Hi,

I sent you the config.log file

Thank you

On 18 aug., 09:58, Monty Taylor <monty.tay...@gmail.com> wrote:
> Can you send me your config.log file?
>
> Also - you might want to use gmake instead of normal solaris make -
> although that is not your problem here.
>
>
>
> On Tue, Aug 17, 2010 at 11:40 PM, Kenton Varda <ken...@google.com> wrote:
> > Sorry, I added Monty Taylor to the CC list.  He's the guy to ask about
> > protobufs on Solaris.
>
> > On Tue, Aug 17, 2010 at 11:16 PM, Vali <valentin.adr...@gmail.com> wrote:
>
> >> Did you wrote something ?
>
> >> On Aug 18, 3:44 am, Kenton Varda <ken...@google.com> wrote:
> >> > On Tue, Aug 17, 2010 at 7:18 AM, Vali <valentin.adr...@gmail.com> wrote:
> >> > > Hi,
>
> >> > > I'm trying to compile protobuffers but i'm having some problems at
> >> > > make...
>
> >> > > Here are some informations about the errors :
>
> >> > > I run configure with the following parameters and it doesn't show any
> >> > > errors..
>
> >> > > bash-3.00$ ./configure CC=/opt/SUNWspro/bin/cc --disable-64bit-solaris
> >> > > checking build system type... sparc-sun-solaris2.10
> >> > > checking host system type... sparc-sun-solaris2.10
> >> > > checking target system type... sparc-sun-solaris2.10
> >> > > checking for a BSD-compatible install... ./install-sh -c
> >> > > checking whether build environment is sane... yes
> >> > > checking for a thread-safe mkdir -p... ./install-sh -c -d
> >> > > checking for gawk... no
> >> > > checking for mawk... no
> >> > > checking for nawk... nawk
> >> > > checking whether dmake sets $(MAKE)... yes
> >> > > checking for gcc... /opt/SUNWspro/bin/cc
> >> > > checking for C compiler default output file name... a.out
> >> > > checking whether the C compiler works... yes
> >> > > etc...
>
> >> > > The errors appear when running make...
>
> >> > > bash-3.00$ make
> >> > > etc...
> >> > > Undefined                       first referenced
> >> > >  symbol                             in file
> >> > > cos                                 /opt/SUNWspro/lib/stlport4/
> >> > > libstlport.so
> >> > > exp                                 /opt/SUNWspro/lib/stlport4/
> >> > > libstlport.so
> >> > > log                                 /opt/SUNWspro/lib/stlport4/
> >> > > libstlport.so
> >> > > sin                                 /opt/SUNWspro/lib/stlport4/
> >> > > libstlport.so
> >> > > cosh                                /opt/SUNWspro/lib/stlport4/
> >> > > libstlport.so
> >> > > sinh                                /opt/SUNWspro/lib/stlport4/
> >> > > libstlport.so
> >> > > sqrt                                /opt/SUNWspro/lib/stlport4/
> >> > > libstlport.so
> >> > > etc...
>
> >> > > ld: fatal: Symbol referencing errors. No output written to .libs/
> >> > > libprotobuf.so.6.0.0
> >> > > *** Error code 1
> >> > > dmake: Fatal error: Command failed for target `libprotobuf.la'
> >> > > Current working directory ../protobuf-2.3.0/src
> >> > > *** Error code 1
> >> > > The following command caused the error:
> >> > > failcom='exit 1'; \
> >> > > for f in x $MAKEFLAGS; do \
> >> > >  case $f in \
> >> > >    *=* | --[!k]*);; \
> >> > >    *k*) failcom='fail=yes';; \
> >> > >  esac; \
> >> > > done; \
> >> > > dot_seen=no; \
> >> > > target=`echo all-recursive | sed s/-recursive//`; \
> >> > > list='. src'; for subdir in $list; do \
> >> > >  echo "Making $target in $subdir"; \
> >> > >  if test "$subdir" = "."; then \
> >> > >    dot_seen=yes; \
> >> > >    local_target="$target-am"; \
> >> > >  else \
> >> > >    local_target="$target"; \
> >> > >  fi; \
> >> > >  (cd $subdir && dmake  $local_target) \
> >> > >  || eval $failcom; \
> >> > > done; \
> >> > > if test "$dot_seen" = "no"; then \
> >> > >  dmake  "$target-am" || exit 1; \
> >> > > fi; test -z "$fail"
> >> > > dmake: Fatal error: Command failed for target `all-recursive'
>
> >> > > Thats about all.
>
> >> > > --
> >> > > 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.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.
> >> 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