Date: Sat, 20 Apr 2002 01:53:09 +0900 From: Hye-Shik Chang <perky@fallin.lv> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: ports@FreeBSD.ORG Subject: Re: icc-compiled Python Message-ID: <20020420015309.A31482@fallin.lv> In-Reply-To: <200204190930.g3J9UET0000796@Magelan.Leidinger.net>; from Alexander@Leidinger.net on Fri, Apr 19, 2002 at 11:30:14AM %2B0200 References: <20020419073658.A32996@fallin.lv> <200204190930.g3J9UET0000796@Magelan.Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 19, 2002 at 11:30:14AM +0200, Alexander Leidinger wrote:
> Great. Do you have any patches do do it in an automated way?
I'm trying to create script to automate it.
but, it is becoming quick and dirty one.. ;)
> > (on compiling with icc, I compiled 6 sources with gcc by hand
> > to avoid icc's error hehe.)
>
> Which files and which errors?
1. fail on CC=icc ./configure
: just configure with gcc and modify Makefile manually
not clear but it works. ;)
2. some warning messages
: removed -fPIC and -W... options.
(but dynamic linking is working without any problem. ehm.)
3. fails linking on two points (Parser/pgen and libpython2.2.a)
: do with gcc manually
4. icc error on FreeBSD base headers on some modules
(including Modules/_localemodule.c Modules/socketmodule.c
Modules/_sslmodule.c)
: compile with gcc manually
Everything worked fine except those.
> Which CPU?
Intel Pentium III 800MHz.
> Any chance the files you compiled with gcc instead of icc are related to
> those tests?
Ah. if Intel allows to distribute icc-compiled binaries.
I didn't read icc license agreement carefully.
>
> Bye,
> Alexander.
>
Thank you!
--
Hye-Shik Chang <perky@fallin.lv>
Yonsei University, Seoul
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020420015309.A31482>