setenv buffer limit in csh

It appears that there is a problem using setenv in csh. If I setenv on a variable and the data value is more than some amount of predefined characters (probably 1024), I get the following error from csh:  "Word too long."

Is there a way I can get around this problem ? The reason is that I have a file that I sourced. Inside this file is a number of setenv statements. After sourcing this file, the script calls up a GNU Makefile with those env. variables passed into it.
Who is Participating?
Klaas082598Connect With a Mentor Commented:
This seems to be a hardcoded limit in both csh and also in tcsh (a public domain (better) csh).
Sidenote: ksh and sh have no problems with longer than 1024 env var's. Maybe their limit is higher.
So one solution could be to rewrite everything to use sh or ksh.

But i don't understand the question completely:
If the setenv statements worked in the first
place, how can they not work lateron ?
What has make got to do with it ?
This could also be a kernel parameter.
On IRIX 5.x you may change it with the systune command,
see man systune, parameter  nc_args.
On SunOS 4.x there is also a kernel parameter, but the kernel
must be rebuild to change it.
I'm not shure, but there was something similar on Solaris.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.