Noriyuki,

1) Why are you creating source and binary on CentOS 6 with the "--with
cnt5064" (CentOS 5) option?
2) Why are you creating CentOS 6 source and binary with a CentOS 5 spec
file?
3) You can also get rid of the "--target x86_64" option if you're
already on an x86_64 architecture, right?
 
For CentOS 6 you need this RPM that has been tailored for it by Eric
Shubert:
http://mirrors.qmailtoaster.com/current/SRPMS/vqadmin-2.3.7-0.qt.src.rpm
Build it with this option:
rpmbuild --rebuild --define "dist .qt.el6" vqadmin-2.3.7-0.qt.src.rpm

Eric


On 7/8/2015 8:16 AM, Noriyuki Hayashi wrote:
> Hi
>
> Environment
> CentOS-6.6 x86_64
> I tried rpmbuild as follow.
> rpmbuild -ba --sign --with cnt5064 --target x86_64 --define "dist .cs6"  
> vqadmin-toaster-2.3.7-1.4.1.spec
> spec file is original.
>
> Then happen this error...
>
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> /home/wats/centos/BUILD/vqadmin-2.3.7/missing: Unknown `--run' option
> Try `/home/wats/centos/BUILD/vqadmin-2.3.7/missing --help' for more 
> information
> configure: WARNING: `missing' script is too old or missing
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking build system type... Invalid configuration 
> `x86_64-redhat-linux-gnu': machine `x86_64-redhat-linux' not recognized
> configure: error: /bin/sh ./config.sub x86_64-redhat-linux-gnu failed
> error: Bad exit status from /var/tmp/rpm-tmp.5rFN0P (%build)
>
> Would you please advice or hints ?
> Thank you so much.
>
> Nori(WATS)
>
> /_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>
>               WATS CO.,LTD.   
> /_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to