From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13128 invoked by alias); 28 Feb 2012 11:48:03 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 16811 Received: (qmail 1667 invoked from network); 28 Feb 2012 11:48:01 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_LOW,T_DKIM_INVALID autolearn=ham version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 209.85.210.171 as permitted sender) Received-SPF: pass (google.com: domain of ismail@namtrac.org designates 10.50.186.198 as permitted sender) client-ip=10.50.186.198; Authentication-Results: mr.google.com; spf=pass (google.com: domain of ismail@namtrac.org designates 10.50.186.198 as permitted sender) smtp.mail=ismail@namtrac.org; dkim=pass header.i=ismail@namtrac.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=namtrac.org; s=www; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=NBwzpX9CoaApQCEPBsuLxLdwImSSXEwhJ9vz69CJIck=; b=UnJWlxxEAaIdbRoDYo1wBcj9npNO7fNVsI4wZ2JEVoLiGjyVCLb7zf42zvXBzTBB7j 63zLksjBMrFnGMtZ0afNZQqSLZ7zyFX0v8oyNM3F7Q3XOaNtlNWNOWNDC0v2/VsqcUP0 jIQRtmbD7pck7kEgLG24byEXWXCCIAl5DJ8Og= MIME-Version: 1.0 In-Reply-To: References: From: =?UTF-8?B?xLBzbWFpbCBEw7ZubWV6?= Date: Tue, 28 Feb 2012 12:47:32 +0100 Message-ID: Subject: Re: Problem with gcc -### To: =?UTF-8?B?SsOpcsOpbWllIFJvcXVldA==?= Cc: Zsh Users Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkG9nPrEpR6Di5SaybJgCG3pIn14/M/uq54Kcc82sbNMCrHmfNXWjCs0kdV4cOJ7IRPkGRF Hi; On Tue, Feb 28, 2012 at 11:53 AM, J=C3=A9r=C3=A9mie Roquet wrote: > Hi, > > 2012/2/28 =C4=B0smail D=C3=B6nmez : >> So turns out that gcc has an interesting option, >> >> in bash: >> >>> gcc -### >> Using built-in specs. >> COLLECT_GCC=3Dgcc >> COLLECT_LTO_WRAPPER=3D/usr/lib64/gcc/x86_64-suse-linux/4.6/lto-wrapper >> Target: x86_64-suse-linux >> Configured with: ../configure --prefix=3D/usr --infodir=3D/usr/share/inf= o >> --mandir=3D/usr/share/man --libdir=3D/usr/lib64 --libexecdir=3D/usr/lib6= 4 >> --enable-languages=3Dc,c++,objc,fortran,obj-c++,java,ada >> --enable-checking=3Drelease --with-gxx-include-dir=3D/usr/include/c++/4.= 6 >> --enable-ssp --disable-libssp --disable-plugin --with-bugurl=3D >> http://bugs.opensuse.org/ --with-pkgversion=3D'SUSE Linux' --disable-lib= gcj >> --disable-libmudflap --with-slibdir=3D/lib64 --with-system-zlib >> --enable-__cxa_atexit --enable-libstdcxx-allocator=3Dnew >> --disable-libstdcxx-pch --enable-version-specific-runtime-libs >> --enable-linker-build-id --program-suffix=3D-4.6 --enable-linux-futex >> --without-system-libunwind --with-arch-32=3Di586 --with-tune=3Dgeneric >> --build=3Dx86_64-suse-linux >> Thread model: posix >> gcc version 4.6.2 20111212 [gcc-4_6-branch revision 182222] (SUSE Linux) >> >> in zsh: >> >> [~]> echo $ZSH_VERSION >> 4.3.15 >> >> [~]> gcc -### >> zsh: bad pattern: -### >> >> Just a minor annoyance but I wanted to share in case its a bug. > > That's because of extended globing. > > You should unsetopt extendedglob or use: > > noglob gcc -### That explains it, thanks a lot!