This is the mail archive of the 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]

other/7956: unreadable error on -m64 with --disable-multilib

>Number:         7956
>Category:       other
>Synopsis:       unreadable error on -m64 with --disable-multilib
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 17 18:06:01 PDT 2002
>Originator:     Benoit Hudson
>Release:        3.2
It'd be nice if the specs recognized that -m64 is an error when gcc has been built with --disable-multilib, rather than giving:
ld: fatal: file /usr/lib/sparcv9/values-Xa.o: cannot open file: No such file or directory
ld: fatal: file /var/tmp//ccKb4eqM.o: wrong machine class
ld: fatal: File processing errors. No output written to a.out
collect2: ld returned 1 exit status

Which is hard for gcc users to understand, if they haven't themselves built gcc.
# build gcc with --disable-multilib
echo "int main() { return 0; }" > foo.c
gcc -m64 foo.c
in the specs, replace all the instances of m64 doing something with %e64-bit support disabled
or somesuch.

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