This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
c/9653: invalid detection of "cannot specify -o with -c or -S and multiple compilations" condition
- From: ianw at gelato dot unsw dot edu dot au
- To: gcc-gnats at gcc dot gnu dot org
- Date: 11 Feb 2003 03:54:31 -0000
- Subject: c/9653: invalid detection of "cannot specify -o with -c or -S and multiple compilations" condition
- Reply-to: ianw at gelato dot unsw dot edu dot au
>Number: 9653
>Category: c
>Synopsis: invalid detection of "cannot specify -o with -c or -S and multiple compilations" condition
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Feb 11 03:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: ianw@gelato.unsw.edu.au
>Release: gcc version 3.3 20030129
>Organization:
>Environment:
IA64 Linux
>Description:
This rather complex command line (below) is given by glibc to build a generated header file. Somewhere gcc 3.3 is thinking it is doing something like
gcc -S -o file test1.c test2.c
This same command line (below) works fine with gcc 3.2. I'm sorry but I don't know exactly what is causing this, but it is repeatable. I have stripped out all the -I's to make the command line more readable. Hopefully you can see where the problem is.
--other cruft --
gawk -f ../scripts/gen-as-const.awk
../linuxthreads/sysdeps/ia64/tcb-offsets.sym \ |
-- gcc command line --
gcc -S -o - -std=gnu99 -O2 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -g [lots of -I's] -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DHAVE_INITFINI -D_ASM_IA64_CURRENT_H -x c - -MD -MF /home/ianw/libc-normal/tcb-offsets.h.dT -MT '/home/ianw/libc-normal/tcb-offsets.h.d /home/ianw/libc-normal/tcb-offsets.h'
-- more non relevant things --
| sed -n
's/^.*@@@name@@@\([^@]*\)@@@value@@@[^0-9Xxa-fA-F-]*\([0-9Xxa-fA-F-][0-9Xxa-fA-F-]*\).*@@@end@@@.*$/#define
\1 \2/p' > /home/ianw/libc-normal/tcb-offsets.hT
with 3.3 the error is
gcc: cannot specify -o with -c or -S and multiple compilations
with 3.2 there is no error and the output is as expected.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: