[Devel] Re: [Users] action.c:1: error: bad value (x86_64) for -mtune= switch

[Bogdan-Andrei Iancu]

just for the list info: the problem was a name overlapping between an 
environment vvariable and a local variable used by make file to set the 
-mtune param - both are named CPU.

the solution to avoid such problem in the future will be to change in 
name of the internal variable in the make file.

regards,
bogdan

Bogdan-Andrei Iancu wrote:

> Hi Ronald,
>
> not sure how the -mtune gets to "x86_64" value. According to 
> Makefile.defs, if the ARCH is x86_64, for gcc 4.x, the CPU will be set 
> to "opteron" and -mtune the same...
>
> have you changed something in the file??
>
> regards,
> Bogdan
>
> Ronald Wiplinger wrote:
>
>> nick wrote:
>>
>>> Ronald Wiplinger wrote:
>>>
>>>> First try to compile Openser on an AMD Semperon CPU:
>>>>
>>>> openser-1.1.0-tls> make all
>>>> Compiling action.c
>>>> gcc -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-stringops 
>>>> -falign-loops -ftree-vectorize -mtune=x86_64    -DNAME='"openser"' 
>>>> -DVERSION='"1.1.0-notls"' -DARCH='"x86_64"' -DOS='"linux"' 
>>>> -DCOMPILER='"gcc 4.1.0"' -D__CPU_x86_64 -D__OS_linux -D__SMP_no 
>>>> -DCFG_DIR='"/usr/local/etc/openser/"' -DPKG_MALLOC -DSHM_MEM  
>>>> -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE 
>>>> -DHAVE_RESOLV_RES -DF_MALLOC -DSTATISTICS  -DFAST_LOCK 
>>>> -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  -DHAVE_GETHOSTBYNAME2 
>>>> -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL 
>>>> -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM 
>>>> -DHAVE_EPOLL -DHAVE_SIGIO_RT -DHAVE_SELECT -c action.c -o action.o
>>>> action.c:1: error: bad value (x86_64) for -mtune= switch
>>>> make: *** [action.o] Error 1
>>>>
>>>>
>>>> How can I solve that?
>>>>
>>>> bye
>>>>
>>>> Ronald
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at openser.org
>>>> http://openser.org/cgi-bin/mailman/listinfo/users
>>>>
>>> GCC 4.1???
>>>
>>> The manual says these are your options for the -mtune switch
>>>
>>> k6
>>>     AMD K6 CPU with MMX instruction set support.
>>> k6-2, k6-3
>>>     Improved versions of AMD K6 CPU with MMX and 3dNOW! instruction 
>>> set support.
>>> athlon, athlon-tbird
>>>     AMD Athlon CPU with MMX, 3dNOW!, enhanced 3dNOW! and SSE 
>>> prefetch instructions support.
>>> athlon-4, athlon-xp, athlon-mp
>>>     Improved AMD Athlon CPU with MMX, 3dNOW!, enhanced 3dNOW! and 
>>> full SSE instruction set support.
>>> k8, opteron, athlon64, athlon-fx
>>>     AMD K8 core based CPUs with x86-64 instruction set support. 
>>> (This supersets MMX, SSE, SSE2, 3dNOW!, enhanced 3dNOW! and 64-bit 
>>> instruction set extensions.)
>>>
>>> so there is no x86_64 (or x86-64) cpu type in 4.1
>>>
>>
>>
>>
>>
>>
>> I got a hint, but I do not know how to implement that:
>>
>>> so there is no x86_64 (or x86-64) cpu type in 4.1
>>>   Not true. There is no x86_64, but while x86-64 is deprecated, it 
>>> is still permissable. If you are building code for the platform you 
>>> are running on, then you can use one of the -mtune=k8 or 
>>> -mtune=generic or -mtune=prescott, or simply let the compiler figure 
>>> it out. Or better use the -m64 option which will cause the compiler 
>>> to build for a generic x86-64 platform. 
>>
>>
>>
>> Can anybody tell me how to do that? (And can you please add the 
>> solution to the next development tree.)
>>
>> bye
>>
>> Ronald
>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/devel
>>
>
>
> _______________________________________________
> Devel mailing list
> Devel at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/devel
>