Sponsored Content
Top Forums UNIX for Dummies Questions & Answers execvp:ar:Arg list too long -> while linking Post 302072544 by jim mcnamara on Wednesday 3rd of May 2006 11:08:50 PM
Old 05-04-2006
Basically it means too many objects on the command line, ie., probably too many arguments.

Are you using a makefile with recursion?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

arg list too long

I do ls -l ABC*, I get arg list too long message. This will not happen if ABC* has small no of files I believe 4000 files is limit. Any way of avoiding this. I even tried like this for i in `ls -l ABC*` do echo $i done Same problem. Any solution would be great. I am on HP-UX... (5 Replies)
Discussion started by: vingupta
5 Replies

2. UNIX for Dummies Questions & Answers

zcat --> Arg list too long

Hi all I have more than 1000 files in a folder and when ever i use a "compress" or "zcat" command it give error /bin/zcat: Arg list too long. . any solution for this :o (3 Replies)
Discussion started by: muneebr
3 Replies

3. UNIX for Advanced & Expert Users

arg list too long

Does anyone have a solution for arg list too long error. I have got this from the web but I fail to make any sense out of it Thanks enc (8 Replies)
Discussion started by: encrypted
8 Replies

4. UNIX for Dummies Questions & Answers

ls -t arg list too long

echo dirname/filename* | xargs ls -t As a substitute doesn't give the results desired when I exceed the buffer size. I still want the files listed in chronological order, unfortunately xargs releases the names piecemeal...does anyone have any ideas? :( (4 Replies)
Discussion started by: CSU_Ram
4 Replies

5. UNIX for Dummies Questions & Answers

arg list too long when mv files?

hello all i need some help because i am a unix/linux dummy...i have the following: DIR1> has 121437 files in it with varying dates going back to early April, a sub dir DIR1/DIR2> has 55835 files in it I need to move all files (T*.*) out of DIR1 into DIR2 that are older than today? Ive been... (2 Replies)
Discussion started by: jamos007
2 Replies

6. UNIX for Dummies Questions & Answers

Arg List too Long in SCP

Hey guys. I have a program written in which i am trying to get the files from one remote machine and transferring the files to another remote machine using SCP. It works fine for 50 or 60 files but when the files grows to 250 then i get an error message stating "Arg list too long". #scp -p... (5 Replies)
Discussion started by: chris1234
5 Replies

7. Shell Programming and Scripting

arg list too long

Hi, Help. I have a file that contains a list of users in a file. I want to cat the content of the file and feed it into sed to a preformated report. The error I got is "ksh: /usr/bin/sed: arg list too long" My method below. A=`cat FILE1.txt` B=`echo $A` sed "s#USERLIST#$B#" FILE2 >... (2 Replies)
Discussion started by: Zenwork
2 Replies

8. AIX

gmake[1]: execvp: /bin/sh: Arg list too long

I am having a code which will create archive after build. Ibuild code on IBM AIX 5.3. It supposed to create 2 archive after build. I am getting 1st archive successfully but when build starts for second archive after some processing it throws an following error message- ar cq... (4 Replies)
Discussion started by: milindb
4 Replies

9. Shell Programming and Scripting

arg list too long error

Hello, I'm trying to search through 30,000 files in 1 directory, and am getting the "arg list too long" error. I've searched this forum and have been playing around with xargs and can't get that to work either. I'm using ksh on Solaris. Here's my original code: nawk "/Nov 21/{_=2}_&&_--"... (14 Replies)
Discussion started by: Kristin_in_CO
14 Replies

10. UNIX for Dummies Questions & Answers

Arg list too long

Hello All, I am trying to find a file name with .sh exention from a list of .dat files inside a directory. find /app/folder1/* -name '*.dat'| xargs grep '.sh' ksh: /usr/local/bin/find: arg list too long Please help me finding the command. Thanks (3 Replies)
Discussion started by: tkhan9
3 Replies
Arg(3)								   OCaml library							    Arg(3)

NAME
Arg - Parsing of command line arguments. Module Module Arg Documentation Module Arg : sig end Parsing of command line arguments. This module provides a general mechanism for extracting options and arguments from the command line to the program. Syntax of command lines: A keyword is a character string starting with a - . An option is a keyword alone or followed by an argument. The types of keywords are: Unit , Bool , Set , Clear , String , Set_string , Int , Set_int , Float , Set_float , Tuple , Symbol , and Rest . Unit , Set and Clear keywords take no argument. A Rest keyword takes the remaining of the command line as arguments. Every other keyword takes the following word on the command line as argument. Arguments not preceded by a keyword are called anonymous arguments. Examples ( cmd is assumed to be the command name): - cmd -flag (a unit option) - cmd -int 1 (an int option with argument 1 ) - cmd -string foobar (a string option with argument foobar ) - cmd -float 12.34 (a float option with argument 12.34 ) - cmd a b c (three anonymous arguments: a , b , and c ) - cmd a b -- c d (two anonymous arguments and a rest option with two arguments) type spec = | Unit of (unit -> unit) (* Call the function with unit argument *) | Bool of (bool -> unit) (* Call the function with a bool argument *) | Set of bool Pervasives.ref (* Set the reference to true *) | Clear of bool Pervasives.ref (* Set the reference to false *) | String of (string -> unit) (* Call the function with a string argument *) | Set_string of string Pervasives.ref (* Set the reference to the string argument *) | Int of (int -> unit) (* Call the function with an int argument *) | Set_int of int Pervasives.ref (* Set the reference to the int argument *) | Float of (float -> unit) (* Call the function with a float argument *) | Set_float of float Pervasives.ref (* Set the reference to the float argument *) | Tuple of spec list (* Take several arguments according to the spec list *) | Symbol of string list * (string -> unit) (* Take one of the symbols as argument and call the function with the symbol *) | Rest of (string -> unit) (* Stop interpreting keywords and call the function with each remaining argument *) The concrete type describing the behavior associated with a keyword. type key = string type doc = string type usage_msg = string type anon_fun = string -> unit val parse : (key * spec * doc) list -> anon_fun -> usage_msg -> unit Arg.parse speclist anon_fun usage_msg parses the command line. speclist is a list of triples (key, spec, doc) . key is the option key- word, it must start with a '-' character. spec gives the option type and the function to call when this option is found on the command line. doc is a one-line description of this option. anon_fun is called on anonymous arguments. The functions in spec and anon_fun are called in the same order as their arguments appear on the command line. If an error occurs, Arg.parse exits the program, after printing to standard error an error message as follows: - The reason for the error: unknown option, invalid or missing argument, etc. - usage_msg - The list of options, each followed by the corresponding doc string. Beware: options that have an empty doc string will not be included in the list. For the user to be able to specify anonymous arguments starting with a - , include for example ("-", String anon_fun, doc) in speclist . By default, parse recognizes two unit options, -help and --help , which will print to standard output usage_msg and the list of options, and exit the program. You can override this behaviour by specifying your own -help and --help options in speclist . val parse_argv : ?current:int Pervasives.ref -> string array -> (key * spec * doc) list -> anon_fun -> usage_msg -> unit Arg.parse_argv ~current args speclist anon_fun usage_msg parses the array args as if it were the command line. It uses and updates the value of ~current (if given), or Arg.current . You must set it before calling parse_argv . The initial value of current is the index of the program name (argument 0) in the array. If an error occurs, Arg.parse_argv raises Arg.Bad with the error message as argument. If option -help or --help is given, Arg.parse_argv raises Arg.Help with the help message as argument. exception Help of string Raised by Arg.parse_argv when the user asks for help. exception Bad of string Functions in spec or anon_fun can raise Arg.Bad with an error message to reject invalid arguments. Arg.Bad is also raised by Arg.parse_argv in case of an error. val usage : (key * spec * doc) list -> usage_msg -> unit Arg.usage speclist usage_msg prints to standard error an error message that includes the list of valid options. This is the same message that Arg.parse prints in case of error. speclist and usage_msg are the same as for Arg.parse . val usage_string : (key * spec * doc) list -> usage_msg -> string Returns the message that would have been printed by Arg.usage , if provided with the same parameters. val align : (key * spec * doc) list -> (key * spec * doc) list Align the documentation strings by inserting spaces at the first space, according to the length of the keyword. Use a space as the first character in a doc string if you want to align the whole string. The doc strings corresponding to Symbol arguments are aligned on the next line. val current : int Pervasives.ref Position (in Sys.argv ) of the argument being processed. You can change this value, e.g. to force Arg.parse to skip some arguments. Arg.parse uses the initial value of Arg.current as the index of argument 0 (the program name) and starts parsing arguments at the next ele- ment. OCamldoc 2014-06-09 Arg(3)
All times are GMT -4. The time now is 07:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy