On Friday 2017-06-30 10:46, Sushil Mishra wrote:
>information to handle your system.
>config.guess timestamp = 2008-01-23
>uname -m = s64fx
>[sm@gwmpc1077 VinaLC]$
>-
>-
>Can you please suggest me
On Tuesday 2017-04-18 17:44, Mojca Miklavec wrote:
>On 18 April 2017 at 17:27, Jan Engelhardt wrote:
>>
>> On Tuesday 2017-04-18 17:18, Mojca Miklavec wrote:
>>>I would like to request a patch for config.guess to partially address
>>>some problems experienced when
On Tuesday 2017-04-18 17:18, Mojca Miklavec wrote:
>I would like to request a patch for config.guess to partially address
>some problems experienced when setting
>CC="gcc -arch ppc"
>on Mac OS X 10.4-10.6 i386 or x86_64.
At least on my side of the ocean, when cross-compiling, specifying the
t
On Wednesday 2017-01-11 15:10, jgp wrote:
>the operating system you are using. It is advised that you
>download the most up to date version of the config scripts from
>
>
> http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
>and
>
> http://git.savannah.gnu.org
On Monday 2016-12-05 15:28, Andreas Schwab wrote:
>On Dez 05 2016, Jan Engelhardt wrote:
>
>> On Monday 2016-12-05 14:03, Ben Elliston wrote:
>>>On Mon, Dec 05, 2016 at 01:37:21PM +0100, Andreas Schwab wrote:
>>>
>>>> +aarch64:Linux:*:* | aarch64_be
On Monday 2016-12-05 14:03, Ben Elliston wrote:
>On Mon, Dec 05, 2016 at 01:37:21PM +0100, Andreas Schwab wrote:
>
>> +aarch64:Linux:*:* | aarch64_be:Linux:*:*)
>> +eval $set_cc_for_build
>> +if echo __ILP32__ | $CC_FOR_BUILD -E - 2>/dev/null \
>> +| grep -q __ILP32__
>> +t
On Friday 2016-10-14 21:31, Vijay Trambadia wrote:
>Hi,I am running mingw32 (from msys2 installation) in windows 7 professional 64
>bit OS.
>
>I believe I have the latest version, please find below the version details
>from config.guess:
> $ ./config.guess -v
>GNU config.guess (2004-03-12)
On Sunday 2015-09-13 13:25, Ben Elliston wrote:
>
>However, this was only added to config.sub. It appears that you can
>build software for k1om self-hosted now. Is that correct?
The graphic on page 8 of
http://registrationcenter.intel.com/irc_nas/7689/scif_userguide.pdf ,
showing compilers on th
On Friday 2015-07-17 14:52, Ling, Alan (EMEA COE LHN - Dublin) wrote:
>
>I am trying to run iperf on ESX 5.5 but it doesn’t work…
Well, ESX identifies itself as "VMKernel" rather than "Linux",
and who knows what else they changed to not make it linux.
You can override with --build=x86_64-unknown-
On Wednesday 2015-07-01 13:16, Daniel Peña Perez wrote:
>UNAME_MACHINE = mips
>UNAME_RELEASE = 3.10.12
>UNAME_SYSTEM = Linux
>UNAME_VERSION = #5 Mon May 18 10:15:49 CST 2015
>configure: error: cannot guess build type; you must specify one
>./configure: line 1: sort: not found
>./configure: line 9
On Wednesday 2015-06-03 01:36, James Y Knight wrote:
>On Jun 2, 2015, at 7:03 PM, Jan Engelhardt wrote:
>> If you run a x86_64 or sparc64 kernel, it means your CPU is capable
>> of running instructions like MOV(QWORD) or LDX, respectively. These
>> instructions can be issue
On Tuesday 2015-06-02 21:56, James Y Knight wrote:
>Similar to the situation on x86-64, a sparc64 linux kernel can run a
>32-bit userspace, and when doing so, the triple should be the 32-bit
>variant not the 64-bit variant.
If you run a x86_64 or sparc64 kernel, it means your CPU is capable
of
On Tuesday 2015-05-19 21:30, chris.gefv...@sungard.com wrote:
>
>checking build system type... ./config.guess: unable to guess system type
>This script, last modified 2012-02-10, has failed to recognize
Hardly surprising, given ppc64le is a recent invention.
But, libreoffice-4.4.3.2's config.guess
On Monday 2015-05-04 15:11, Jerry Miller wrote:
>See below; also note that even upgrading to Cygwin 64 does not correct the
>problem of too many (over 50K) object-file sections when making Ingerno:
>
>config.guess timestamp = 2004-09-07
Did they try updating _that_?
On Monday 2015-02-23 14:29, H.J. Lu wrote:
>On Sun, Aug 19, 2012 at 2:47 AM, Ben Elliston wrote:
>>> There are 12 existing set_cc_for_build usages in config.guess. I
>>> don't think it is reasonable to require x32 not to use it without
>>> providing an alternative. If you want to remove set_cc_
On Wednesday 2015-01-21 10:26, 陈磊ChenLee wrote:
>2015-01-21 17:01 GMT+08:00, Jan Engelhardt :
>> On Wednesday 2015-01-21 03:00, 陈磊ChenLee wrote:
>>
>>>config.guess timestamp = 2005-08-03
>>>
>>>uname -m = sw_64
>>>uname -r = 3.8.0-sw2f
>>
On Wednesday 2015-01-21 03:00, 陈磊ChenLee wrote:
>config.guess timestamp = 2005-08-03
>
>uname -m = sw_64
>uname -r = 3.8.0-sw2f
>uname -s = Linux
>uname -v = #1 SMP Mon Aug 4 23:43:46 CST 2014
What kind of CPU is that? It does not appear to be something that
an original Linux has support for.
_
On Friday 2015-01-09 09:21, wilfredo.chung wrote:
>Japan's K computer (Please see attached file)
>
>config.guess timestamp = 2015-01-01
>uname -m = s64fx
>uname -r = 2.6.25.8
>uname -s = Linux
To the best of my understanding, the Fujitsu SPARC VIIIfx is
V9-compatible. An original Linux would repo
On Tuesday 2014-09-09 14:47, Bhramar Vatsa wrote:
>Hi,
>I am working on a windows 7 machine (64-bit). I am trying to build newlib on
>windows native command prompt. When I try to run the configure script with
>following commandline, it fails with an error.
>
>sh.exe"-3.1$ CC=lcc-clang AS=lasm LD=l
On Tuesday 2014-07-29 16:41, linearhit wrote:
>
>I received the following info when i tried to guess the configuration of my
>system.
>The hardware is a router by Netgear, with broadcom BCM4718A and DD-WRT
>firmware.
>
>uname -m = mips
>uname -r = 2.6.24.111
>uname -s = Linux
>uname -v = #465 Tue
On Thursday 2014-04-17 16:38, Orlin Popov wrote:
>This is cygwin 64 on windows 7 64 bit. What is wrong?
^
>
>$ ./config.guess
>./config.guess: unable to guess system type
>
>This script, last modified 2002-07-23, has failed to recognize
^
On Friday 2014-01-31 11:05, Wheatley, Martin R wrote:
>We're investigating two core dumps; both in ui_create_cursor()...
But this is config-patches, not rdesktop..
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/l
On Wednesday 2013-11-06 00:26, Mojca Miklavec wrote:
>
>The role of config.guess should be figuring out what architecture we
>are compiling *for* (that could easily be i386 or ppc even on x86_64).
This has come up before on the config-patches list[1]. config.guess's
job is not to tell you what yo
On Tuesday 2013-10-22 03:43, Daniel Richard G. wrote:
>On Mon, 2013 Oct 21 18:13+0800, JonY wrote:
>
>In the same way that, on a Solaris machine I work with here, I can get
>
>$ ./config.guess
>i386-pc-solaris2.10
>$ CC="cc -xarch=generic64" ./config.guess
>x86_64-pc-solaris2.10
On Tuesday 2013-05-21 07:33, Pavel Raiskup wrote:
>> Works for me. But we [distros] do want to mandate autoreconf anyway in the
>> general case: it is the *only* way to keep upstream honest about the much
>> hated build system not bitrotting until it decides to blow up right when we
>> need it f
On Tuesday 2013-02-12 12:19, Yann Droneaud wrote:
>Le mardi 05 février 2013 à 19:15 +0100, Jan Engelhardt a écrit :
>> On Sunday 2013-02-03 10:49, Yann Droneaud wrote:
>> >
>> >So to create a "valid" --build argument, I was going to use
>> >--build=`
On Sunday 2013-02-03 10:49, Yann Droneaud wrote:
>
>I tried to explain the reasonning behind those patches in the following
>thread:
>http://lists.gnu.org/archive/html/config-patches/2013-02/msg2.html
>
>Those patches are to be used as part of a kind of a workaround for the
>need to give a --b
On Friday 2013-02-01 16:23, Yann Droneaud wrote:
>
>The rationale behind this is:
>
>when using ./configure --host=, --build=,--target=,
> is not the output of config.guess and can be written in
>upper-case. For example ./configure --host=X86-LINUX
But the question is: why would anybody want to
28 matches
Mail list logo
