# Setenv: Too many arguments

**URL:** <https://forum.cmascenter.org/t/setenv-too-many-arguments/2033>\
**Category:** CMAQ\
**Created:** [January 28, 2021, 6:55am UTC](https://forum.cmascenter.org/t/setenv-too-many-arguments/2033 "2021-01-28T06:55:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rainzmh](https://avatars.discourse-cdn.com/v4/letter/r/b5a626/32.png) [@Rainzmh](https://forum.cmascenter.org/u/Rainzmh)\
**Post date:** [January 28, 2021, 6:55am UTC](https://forum.cmascenter.org/t/setenv-too-many-arguments/2033/1 "2021-01-28T06:55:44Z")

</div>

When I am installing CMAQ5.3, the step that I type `./config_cmaq.csh gcc 7.5.0` or `./config_cmaq.csh gcc` ,the error occur that

> Compiler is set to gcc  
> setenv: Too many arguments.

this is my file of config\_cmaq.csh.[config\_cmaq.csh](https://forum.cmascenter.org/uploads/short-url/s0zgCtBqWsxARpUCEDLniG0nr1X.csh) (10.7 KB)

---

<div class="post-metadata">

**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\
**Post date:** [January 28, 2021, 12:28pm UTC](https://forum.cmascenter.org/t/setenv-too-many-arguments/2033/2 "2021-01-28T12:28:01Z")

</div>

I don’t see it immediately, but the obvious thing is to put the statement

`set echo`

at line 2 of the script, and find out exactly where the script goes wrong.

---

<div class="post-metadata">

**Author:** ![hogrefe.christian](https://avatars.discourse-cdn.com/v4/letter/h/74df32/32.png) [@hogrefe.christian](https://forum.cmascenter.org/u/hogrefe.christian)\
**Post date:** [January 29, 2021, 12:25am UTC](https://forum.cmascenter.org/t/setenv-too-many-arguments/2033/3 "2021-01-29T00:25:37Z")

</div>

Looks like this line in the “case gcc” block is the culprit:

> setenv myLINK\_FLAG “-fopenmp” openMP not supported w/ CMAQ

Looking at the blocks for the other compiler cases, this should probably be changed to

> setenv myLINK\_FLAG #“-fopenmp” openMP not supported w/ CMAQ

---

<div class="post-metadata">

**Author:** ![cjcoats](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cjcoats](https://forum.cmascenter.org/u/cjcoats)\
**Post date:** [January 29, 2021, 4:07pm UTC](https://forum.cmascenter.org/t/setenv-too-many-arguments/2033/4 "2021-01-29T16:07:26Z")

</div>

Or better:  
`setenv myLINK_FLAG "-fopenmp"`  
and simioloarly for the other compiler-choices.

The default I/O API supports OpenMP applications, in particular ones in M3Tools, SMOKE, and others outside EPA (MAQSIP, AHRMS, REFLEX); these link flags do NOT adversely affect the operation of CMAQ; and this OpenMP support has been in place for more than 24 years. CMAQ should not be going off in its own way on this.

`openMP not supported w/ CMAQ` is bogus and irrelevant. If you don’t use OpenMP, then linking it in because it’s needed for other applications will have no impact on CMAQ performance.

Insisting on special builds just for CMAQ is lousy engineering. No: lousy **hacking**. (Think about other “system” libraries: do you want a particular custom _libc_? Good luck with that!)