Problems compiling with hipe

Chandrashekhar Mullaparthi Chandrashekhar.Mullaparthi@REDACTED
Wed Sep 19 16:46:05 CEST 2001


The function exported from big.h is uint_to_big - not uint32_to_big. I
grepped thru the code and couldn't find a reference to uint32_to_big
anywhere and uint_to_big appears only in big.h. Try changing one to the
other and recompile.


> -----Original Message-----
> From: Sean Hinde [mailto:Sean.Hinde@REDACTED]
> Sent: 19 September 2001 15:27
> To: 'Erlang Questions'
> Subject: Problems compiling with hipe
> Hi,
> When compiling on Solaris 7 with --enable-hipe I get the 
> following message
> when it tries to link beam:
> Undefined                       first referenced
>  symbol                             in file
> uint32_to_big
> /export/home/sean/lib/otp_src_P8A-20010913-S
> NAPSHOT/erts/obj.beam/sparc-sun-solaris2.7/hipe_bif0.o
> ld: fatal: Symbol referencing errors. No output written to
> /export/home/sean/lib
> /otp_src_P8A-20010913-SNAPSHOT/bin/sparc-sun-solaris2.7/beam
> collect2: ld returned 1 exit status
> make[3]: ***
> [/export/home/sean/lib/otp_src_P8A-20010913-SNAPSHOT/bin/sparc-sun-
> solaris2.7/beam] Error 1
> Before this I got the perhaps related message:
> gcc  -g -O3
> -I/export/home/sean/lib/otp_src_P8A-20010913-SNAPSHOT/erts/sparc-sun
> -solaris2.7  -DHAVE_CONFIG_H -Wall -DHIPE_ARCHITECTURE=ultrasparc
> -Wa,-xarch=v8p
> lusa -Ibeam -Isys/unix -Isparc-sun-solaris2.7 -Izlib -Ihipe -c
> hipe/hipe_bif0.c
> -o
> /export/home/sean/lib/otp_src_P8A-20010913-SNAPSHOT/erts/obj.b
> eam/sparc-sun-
> s
> olaris2.7/hipe_bif0.o
> hipe/hipe_bif0.c: In function `Uint32_to_term':
> hipe/hipe_bif0.c:64: warning: implicit declaration of function
> `uint32_to_big'
> Anyone any ideas? From a brief look at the hipe_bif0.c file 
> all looks fine..
> big.h is included and this exports the uint32_to_big function..
> Stuck,
> Sean

This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.

More information about the erlang-questions mailing list