error with configure (svn 64857)

[Mathieu Prevot]

Hi,

I have the following error when I run configure:

checking size of wchar_t... configure: error: cannot compute sizeof (wchar_t)

what can I do ?

Mathieu

 

[Martin v. Löwis]

I have the following error when I run configure:

checking size of wchar_t... configure: error: cannot compute sizeof (wchar_t)

what can I do ?

Study config.log for the source of the problem.

Regards,
Martin

 

[Mathieu Prevot]

Study config.log for the source of the problem.

Thank you Martin. How can I remove -lgcc_s and use the Intel equivalent ?

configure:21939: checking for wchar_t
configure:21970: icc -c -g -O2 conftest.c >&5
conftest.c(123): warning #279: controlling expression is constant
if ((ac__type_new_ *) 0)
^

configure:21976: $? = 0
configure:21991: result: yes
configure:21998: checking size of wchar_t
configure:22306: icc -o conftest -g -O2 conftest.c >&5
ld: library not found for -lgcc_s
configure:22309: $? = 1
configure: program exited with status 1

Mathieu

 

[WDC]

Thank you Martin. How can I remove -lgcc_s and use the Intel equivalent ?

configure:21939: checking for wchar_t
configure:21970: icc -c -g -O2  conftest.c >&5
conftest.c(123): warning #279: controlling expression is constant
  if ((ac__type_new_ *) 0)
      ^

configure:21976: $? = 0
configure:21991: result: yes
configure:21998: checking size of wchar_t
configure:22306: icc -o conftest -g -O2   conftest.c  >&5
ld: library not found for -lgcc_s
configure:22309: $? = 1
configure: program exited with status 1

Mathieu

I think he wanted YOU to find the problem. The best way to learn is to
figure it out yourself! Good luck.

 

[Martin v. Löwis]

Thank you Martin. How can I remove -lgcc_s and use the Intel equivalent ?

I'm not so sure that there is anything wrong in configure. configure
doesn't pass -lgcc_s to icc; instead, icc is making this up on its
own. So I would guess you need to get libgcc_s onto you system in a
way that the linker finds it. Else you need to read the icc
documentation (but I'm fairly sure that icc is *required* to link
with libgcc_s, for interoperability with gcc-compiled binaries).

I'm somewhat puzzled that the wchar_t test is the one where it
crashes; this test comes fairly late, and configure has run multiple
compiler invocations before that.

Can you build any binaries at all with your icc installation?

Regards,
Martin

 

[Mathieu Prevot]

I'm not so sure that there is anything wrong in configure. configure
doesn't pass -lgcc_s to icc; instead, icc is making this up on its
own. So I would guess you need to get libgcc_s onto you system in a
way that the linker finds it. Else you need to read the icc
documentation (but I'm fairly sure that icc is *required* to link
with libgcc_s, for interoperability with gcc-compiled binaries).

I'm somewhat puzzled that the wchar_t test is the one where it
crashes; this test comes fairly late, and configure has run multiple
compiler invocations before that.

Can you build any binaries at all with your icc installation?

Yes of course, I successfuly built and installed nmap, wget, so I
thought there was something in the python configure process.

If didn't investigate everything but I solved the problem by adding
the "-static-libgcc" option:

CFLAGS="-w -static-intel -static-libgcc"

I think one should commit changes so configure can manage this. I can
I want to help for further diagnosis or improvement. Also it seems
-Wall will be deprecated, and usually we use -w:

-w<n> Control diagnostics, where <n> is one of the following:

0 -- Display errors (same as -w)

1 -- Display warnings and errors (default)

2 -- Display remarks, warnings, and errors


Cheers,
Mathieu

 

[Mathieu Prevot]

I think he wanted YOU to find the problem. The best way to learn is to
figure it out yourself! Good luck.

Yes WDC I know, but for some problems 1) we can gain much efficiency
with getting help from guys that are familiar with the environment and
2) we also allow the committers to know a problem and improve the
sources. That's the way an open source group works IMHO

Now that the problem is solved for me, it is for all MacOSX+Intel icc guys.

Cheers,
Mathieu

 

[Martin v. Löwis]

If didn't investigate everything but I solved the problem by adding

the "-static-libgcc" option:

CFLAGS="-w -static-intel -static-libgcc"

I think one should commit changes so configure can manage this.

I don't think that change should be made. I'm almost certain that it is
correct. Many people build Python with icc, and never reported any such
problem. So there must something be wrong with your icc installation.

Regards,
Martin