Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

post-simulation using VCS error "Argument list too lo

Status
Not open for further replies.

yurenjie

Newbie level 3
Joined
Jul 17, 2009
Messages
4
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,301
HI,all!
when I implement an arm soc system post-simulation with VCS,therer is an error happans,as follows:
make:execvp:g++:Argument list too long
make:***[product_timestamp]Error 127
Make exited with status 2
---
can anyone tell me reason of this error and the solution?

Regards!!
 

skyfaye

Member level 5
Joined
Feb 25, 2008
Messages
82
Helped
25
Reputation
50
Reaction score
11
Trophy points
1,288
Activity points
1,876
Re: post-simulation using VCS error "Argument list to

Doc Id: 017218 Product: VCS
Last Modified: 04/07/2006 Print-Friendly Version Email Article

My Saved Articles
Rate this article: Not Useful Somewhat Useful Useful Very Useful
Argument list too long

Question:

I get the following message during linking:

make: execvp: gcc: Argument list too long
make: *** [product_timestamp] Error 127


Answer:

By default VCS compiles module definitions into individual object files
and sends all the object files in a command line to the linker. Some
platforms use a fixed-length buffer for the command line, and if VCS sends
too long a list of object files, this buffer overflows and the link fails.

A solution to this problem is to have the linker create temporary object
files containing more than one module definition so there are fewer object
files on the linker command line. You enable creating these temporary object
files, and specify how many module definitions are in these files, with the
following option

-Marchive=N

where N is the number of modules definitions to include in one temporary
object file.

i.e.

% vcs -f filelist.f -Marchive=100 ...

Using this option briefly doubles the amount of disk space used by the linker
because the object files containing more than one module definition are
copies of the object files for each module definition. After the linker
creates the simv executable it deletes the temporary object files.
 

    yurenjie

    Points: 2
    Helpful Answer Positive Rating

ljxpjpjljx

Advanced Member level 3
Joined
May 5, 2008
Messages
972
Helped
80
Reputation
162
Reaction score
55
Trophy points
1,308
Location
Shang Hai
Activity points
4,679
Re: post-simulation using VCS error "Argument list to

furthermore ,if you can spilt the module more clearly , you can avoid this problem!
 

yurenjie

Newbie level 3
Joined
Jul 17, 2009
Messages
4
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,301
Re: post-simulation using VCS error "Argument list to

skyfaye said:
Doc Id: 017218 Product: VCS
Last Modified: 04/07/2006 Print-Friendly Version Email Article

My Saved Articles
Rate this article: Not Useful Somewhat Useful Useful Very Useful
Argument list too long

Question:

I get the following message during linking:

make: execvp: gcc: Argument list too long
make: *** [product_timestamp] Error 127


Answer:

By default VCS compiles module definitions into individual object files
and sends all the object files in a command line to the linker. Some
platforms use a fixed-length buffer for the command line, and if VCS sends
too long a list of object files, this buffer overflows and the link fails.

A solution to this problem is to have the linker create temporary object
files containing more than one module definition so there are fewer object
files on the linker command line. You enable creating these temporary object
files, and specify how many module definitions are in these files, with the
following option

-Marchive=N

where N is the number of modules definitions to include in one temporary
object file.

i.e.

% vcs -f filelist.f -Marchive=100 ...

Using this option briefly doubles the amount of disk space used by the linker
because the object files containing more than one module definition are
copies of the object files for each module definition. After the linker
creates the simv executable it deletes the temporary object files.


hi,thanks!!!
this question puzzeled me for a long time, thanks for your answer!
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Top