Date: Thu, 5 Apr 2007 12:20:55 +0200 From: usleepless@gmail.com To: "Andriy Gapon" <avg@icyb.net.ua> Cc: freebsd-multimedia@freebsd.org, freebsd-stable@freebsd.org, freebsd-ports@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64: cc -dumpmachine [ffmpeg] Message-ID: <c39ec84c0704050320v23824832sa7b822ea530a2c01@mail.gmail.com> In-Reply-To: <4614C619.8000803@icyb.net.ua> References: <200704050941.l359fTo9092265@lurza.secnetix.de> <4614C619.8000803@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Adriy, On 4/5/07, Andriy Gapon <avg@icyb.net.ua> wrote: > on 05/04/2007 12:41 Oliver Fromme said the following: > > Andriy Gapon wrote: > > > > > > [sorry for spamming so many lists but all of them seem to be relevant] > > > > > > $ uname -srm > > > FreeBSD 6.2-RELEASE-p2 amd64 > > > $ cc -dumpmachine > > > > > > $ > > > > I get the same empty result on a 32bit RELENG_6 (i386) > > machine here. It seems to be normal. > > Maybe "normal" for FreeBSD GCC but not for GCC in general. > E.g.: > $ uname -srm > Linux 2.6.19-1.2895.fc6xen x86_64 > $ cc -dumpmachine > x86_64-redhat-linux > > > > At least configure script of the latest ffmpeg-devel port seems to be > > > confused by this. > > > > Works fine here on said i386 machine. So it must be > > something else, no related to the -dumpmachine output, > > but maybe amd64-related. > > By "confused" I meant that the configure script decided that it > cross-builds for i386 because it didn't see "something 64" in the output > of the said command. So this is it. you are right. and it has been fixed in CURRENT. for the time being, check out the output of "c++ -dumpmachine". you will be surprised. regards, usleep
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c39ec84c0704050320v23824832sa7b822ea530a2c01>