From: Arthur Gold <agold@bga.com>
To: help-gcc@gnu.org
Subject: Re: compiler problem
Date: Thu, 02 Dec 1999 13:44:00 -0000 [thread overview]
Message-ID: <3846E64F.C0D653B9@bga.com> (raw)
In-Reply-To: <825rhv$5vn$1@qvarsx.er.usgs.gov>
Nicole Bogeajis wrote:
>
> I have these programs writen in C that were running on our DG systems. We
> recently moved them to our Sun system. When i try to run them from this new
> location, i get the error
>
> ksh: qw_check.run: cannot execute
>
> It was suggested to me that the reason we are getting this error is that the
> program needs to be re-compiled on the Sun. I was "man"-ing the compile
> command cc on the Sun to try to come up with a compile command on this
> system. The programs were originally compiled with an executable file that
> contained the commands.
>
> esqlc $1.sc
> cc -o $1.run $1.c -L /usr/opt/ingres/lib -l ingres -l sd -l m
> cp $1.run /jaxrpt/RUN/.
> ~
>
Should be: cc -o $1.run $1.c -L/usr/opt/ingres/lib -lingres -lsd -lm
[i.e. lose the spaces]
(assuming the existence of libingres and libsd in /usr/opt/ingres/lib or
somewhere in your path)
HTH,
--ag
> This compile command does not work on the Sun. I get the error:
>
> $ ./make qw_check_new
> ESQL qw_check_new.sc:
> cc1: Invalid option `-L'
> cc1: Invalid option `-l'
> cc1: Invalid option `-l'
> cc1: Invalid option `-l'
> cc1: m: No such file or directory
> cp: cannot access qw_check_new.run
>
> do you know what changes i
> need to make to fix this problem...it was suggested that i use gcc as a
> compiler...sorry for my vagueness on the
> subject...thats about all i know about it.
>
> Thank you for any help or suggestions you could give me
>
> Nicole
> bogeajis@usgs.gov
--
Artie Gold, Austin, TX (finger the cs.utexas.edu account for more info)
mailto:agold@bga.com or mailto:agold@cs.utexas.edu
--
?
WARNING: multiple messages have this Message-ID
From: Arthur Gold <agold@bga.com>
To: help-gcc@gnu.org
Subject: Re: compiler problem
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <3846E64F.C0D653B9@bga.com> (raw)
Message-ID: <19991231222400.W3dJekrwA0q-dqZo2UPXWe9T-D_8C1QQe2JTcXDJ3ZA@z> (raw)
In-Reply-To: <825rhv$5vn$1@qvarsx.er.usgs.gov>
Nicole Bogeajis wrote:
>
> I have these programs writen in C that were running on our DG systems. We
> recently moved them to our Sun system. When i try to run them from this new
> location, i get the error
>
> ksh: qw_check.run: cannot execute
>
> It was suggested to me that the reason we are getting this error is that the
> program needs to be re-compiled on the Sun. I was "man"-ing the compile
> command cc on the Sun to try to come up with a compile command on this
> system. The programs were originally compiled with an executable file that
> contained the commands.
>
> esqlc $1.sc
> cc -o $1.run $1.c -L /usr/opt/ingres/lib -l ingres -l sd -l m
> cp $1.run /jaxrpt/RUN/.
> ~
>
Should be: cc -o $1.run $1.c -L/usr/opt/ingres/lib -lingres -lsd -lm
[i.e. lose the spaces]
(assuming the existence of libingres and libsd in /usr/opt/ingres/lib or
somewhere in your path)
HTH,
--ag
> This compile command does not work on the Sun. I get the error:
>
> $ ./make qw_check_new
> ESQL qw_check_new.sc:
> cc1: Invalid option `-L'
> cc1: Invalid option `-l'
> cc1: Invalid option `-l'
> cc1: Invalid option `-l'
> cc1: m: No such file or directory
> cp: cannot access qw_check_new.run
>
> do you know what changes i
> need to make to fix this problem...it was suggested that i use gcc as a
> compiler...sorry for my vagueness on the
> subject...thats about all i know about it.
>
> Thank you for any help or suggestions you could give me
>
> Nicole
> bogeajis@usgs.gov
--
Artie Gold, Austin, TX (finger the cs.utexas.edu account for more info)
mailto:agold@bga.com or mailto:agold@cs.utexas.edu
--
?
next prev parent reply other threads:[~1999-12-02 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-02 5:42 Nicole Bogeajis
1999-12-02 13:44 ` Arthur Gold [this message]
1999-12-31 22:24 ` Arthur Gold
1999-12-31 22:24 ` Nicole Bogeajis
2005-07-24 19:48 Fred J.
2005-07-24 20:50 ` Alex J. Dam
2005-07-25 16:09 ` Travis Spencer
2005-07-25 20:28 ` Fred J.
2005-07-26 6:08 ` Travis Spencer
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=3846E64F.C0D653B9@bga.com \
--to=agold@bga.com \
--cc=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).