This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/7881] Cannot compile gcc-3.2 on Tru64 4.0G if gnu libiconv is installed


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7881



------- Additional Comments From goebel@emunix.emich.edu  2003-06-11 15:16 -------
Subject: Re:  Cannot compile gcc-3.2 on Tru64 4.0G if gnu libiconv is installed


Hiya,

 Just a reference it does build on another Tru64 4.0g system 
that I have, which dosen't have iconv installed on it.

free() is defined in stdlib.h
memset() is defined in string.h

from config.cache
gcc_cv_have_decl_free=${gcc_cv_have_decl_free='yes'}
ac_cv_func_memset=${ac_cv_func_memset='yes'}

config.log from ./libiberty to followin in seperate message.

Thanks,
Matt

And now a bit of polka music by "dhazeghi@yahoo.com"
> 
> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7881
> 
> 
> 
> ------- Additional Comments From dhazeghi@yahoo.com  2003-06-11 15:05 -------
> Thanks for the feedback. Looks like headers necessary for compilation aren't being included. Ugh. 
> free() and memset() are defined in stdlib.h on Tru64, correct? Can you either attach your config.log 
> from the libiberty build that failed, or check whether these necessary headers are in fact detected? 
> Thanks,
> 
> Dara
> 
> 
> 
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]