( ESNUG 272 Item 2 ) -------------------------------------------- [11/19/97]
Subject: Choice Of C Compiler And Problems With The Synopsys VSS C Interface
From: Fabian Wolf <fabian@vergil.ida.ing.tu-bs.de>
>
> Hi there, after working a lot with the SYNOPSYS C Language Interface CLI
> we are currently encountering problems with the C compiler used. The cc
> does not fit our needs, so we are interested in using the gcc. Does anyone
> know where set the default C compiler for the CLI or the parameters for
> the call as this is not explained in the manual. Renaming the gcc to cc
> helps, but this still does not solve the problem with the fixed parameter
> set in the compiler call.
>
> Any experience on that subject? We would be really grateful for any help.
>
> - Fabian Wolf
> Institut fuer Datenverarbeitungsanlagen
From: ryan@dogbert (Ken Ryan)
I have never used the Synopsys CLI with gcc, but the cli command itself is
merely a shell script. Typing "cli" by itself provides a rundown of
switches and debugging aids (I've found setenv CLIECHO 1 useful). Beyond
that, poring through the cli script itself there seems to be places where
compiler switches are define. This is machine-dependent, so I can't help
you beyond that.
- Kenneth Ryan
Orbital Sciences Corp.
---- ---- ---- ---- ---- ---- ----
From: Chris.Brown@arm.com ( Chris Brown )
You can chose which C compiler VSS uses by editing the following file:
admin/setup/.synopsys_vss.setup
- Chris Brown
Advanced RISC Machines Ltd.
---- ---- ---- ---- ---- ---- ----
From: "Mihai T. LAZARESCU" <mihai@ccmserv.polito.it>
Have you tried to set the environment variable CC=gcc, like:
csh and alike> setenv CC gcc
sh and alike> export CC; CC=gcc
Maybe it helps out.
- Mihai T. LAZARESCU
Politecnico di Torino - Italia
---- ---- ---- ---- ---- ---- ----
From: Jon Connell <jon.connell@hl.siemens.de>
Create a script called "cc" (which works fine for Solaris) like this:
#! /usr/local/bin/perl
$ENV{PATH} = "/opt/gnu_2.0/bin:$ENV{PATH}";
foreach $arg (@ARGV)
{
$arg =~ s/-K//;
$arg =~ s/-*PIC/-fPIC/;
}
exec("gcc @ARGV");
Make sure it's in a directory which is at the beginning of your search path,
and away you go! Other platforms will use different options for the PIC
stuff. Another idea is to edit the cli script (as mentioned in this thread).
- Jon Connell
Siemens HL, Microcomputer ICs
|
|
