From: "Rupert Wood" <me@rupey.net>
To: <carri@polymer.uakron.edu>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: gcc 3.0.4 problem
Date: Tue, 30 Apr 2002 10:55:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D5EC37A@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D5FB439@whale.softwire.co.uk>
Professor Gustavo Carri wrote:
> /usr/local/bin/gcc -o HPL_dlacpy.o -c -fomit-frame-pointer -O3
> -funroll-loops -Dadd_ -DF77_INTEGER=int - DStringSunStyle
> -DHPL_CALL_CBLAS -I/home/gus/hpl/include
> -I/home/gus/hpl/include/Linux_21264_CBLAS_gm /home/gus/ATLAS/include
> -I/home/mpich/include ../HPL_dlacpy.c
:
> gcc: cannot specify -o with -c or -S and multiple compilations
Two mistakes here:
1. there shouldn't be a space between '-' and 'DStringSunStyle'
2. you need an '-I' before '/home/gus/ATLAS/include'
although I appreciate that these may have been introduced copying the
error into your e-mail.
You may have to correct CFLAGS or similar in your makefile.
Rup.
next parent reply other threads:[~2002-04-30 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <616BE6A276E3714788D2AC35C40CD18D5FB439@whale.softwire.co.uk>
2002-04-30 10:55 ` Rupert Wood [this message]
2002-04-30 8:34 Professor Gustavo Carri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=616BE6A276E3714788D2AC35C40CD18D5EC37A@whale.softwire.co.uk \
--to=me@rupey.net \
--cc=carri@polymer.uakron.edu \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).