This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: gcc 4.5.0 libiberty .o vs. .obj confusion
oops, also need like:
--- /src/orig/gcc-4.5.0/libiberty/configure??? 2010-01-04 15:46:56.000000000 -0800
+++ /src/gcc-4.5.0/libiberty/configure??? 2010-05-05 05:40:52.000000000 -0700
@@ -6533,10 +6533,10 @@
?
?# Figure out which version of pexecute to use.
?case "${host}" in
-???? *-*-mingw* | *-*-winnt*)??? pexecute=./pex-win32.o? ;;
-???? *-*-msdosdjgpp*)??? ??? pexecute=./pex-djgpp.o? ;;
-???? *-*-msdos*)??? ??? pexecute=./pex-msdos.o? ;;
-???? *)??? ??? ??? ??? pexecute=./pex-unix.o?? ;;
+???? *-*-mingw* | *-*-winnt*)??? pexecute=./pex-win32.$ac_objext? ;;
+???? *-*-msdosdjgpp*)??? ??? pexecute=./pex-djgpp.$ac_objext? ;;
+???? *-*-msdos*)??? ??? pexecute=./pex-msdos.$ac_objext? ;;
+???? *)??? ??? ??? ??? pexecute=./pex-unix.$ac_objext?? ;;
?esac
?
--- /src/orig/gcc-4.5.0/libiberty/configure.ac??? 2010-01-04 15:46:56.000000000 -0800
+++ /src/gcc-4.5.0/libiberty/configure.ac??? 2010-05-05 05:45:47.000000000 -0700
@@ -671,10 +671,10 @@
?
?# Figure out which version of pexecute to use.
?case "${host}" in
-???? *-*-mingw* | *-*-winnt*)??? pexecute=./pex-win32.o? ;;
-???? *-*-msdosdjgpp*)??? ??? pexecute=./pex-djgpp.o? ;;
-???? *-*-msdos*)??? ??? pexecute=./pex-msdos.o? ;;
-???? *)??? ??? ??? ??? pexecute=./pex-unix.o?? ;;
+???? *-*-mingw* | *-*-winnt*)??? pexecute=./pex-win32.$ac_objext? ;;
+???? *-*-msdosdjgpp*)??? ??? pexecute=./pex-djgpp.$ac_objext? ;;
+???? *-*-msdos*)??? ??? pexecute=./pex-msdos.$ac_objext? ;;
+???? *)??? ??? ??? ??? pexecute=./pex-unix.$ac_objext?? ;;
?esac
?AC_SUBST(pexecute)
?
I manually edited configure.
I don't know how to keep multiple versions of autoconf installed/working, other than to use Cygwin and its special packages dedicated to this problem.
configure.ac:3: error: Autoconf version 2.64 or higher is required
configure.ac:3: the top level
autom4te: /usr/bin/gm4 failed with exit status: 63
jbook2:libiberty jay$
?- Jay
----------------------------------------
> From: jay.krell@
> To: iant@m
> CC: gcc@g
> Subject: RE: gcc 4.5.0 libiberty .o vs. .obj confusion
> Date: Wed, 5 May 2010 10:10:15 +0000
>
>
>> CC: gcc@
>> From: iant@
>>
>> Jay:
>>> I'm guessing that every ".o" in libiberty/Makefile.in should be changed to $(OBJEXT).
>>
>> Yes.
>>
>> Ian
>
> Thanks.
>
> Specifically ".o" goes to ".@OBJEXT@".
>
> There's no way I'm going to be able to get "the papers" in.
> I can try to squeak by via triviality of change.
> I'm slightly derailed on other aspects of targeting VMS (e.g. *crt0*.c, vms-crtl.h), but this did work for me, attached.
> It's many lines, but highly mechanical.
> There are a few places where ".o" occurs in comments, can be left alone.
> There is:
>
> .c.o:
> false
>
>> .c.obj:
>> false
>
>
> and
> < -rm -rf *.o pic core errs \#* *.E a.out
>
>> -rm -rf *.o *.obj pic core errs \#* *.E a.out
>
>
> and I wrapped the affected lines to one file per line, and spaces instead of tabs (consistent rendering)
>
>
> - Jay
>