still have same problem.
>
> Can you please run the latest version, then, and send the output of that
> script?
>
In other words
>> config.guess timestamp = 2003-06-17
isn't the latest version.
--
Earnie
___
config-patches
two files. Often packages that depend on
other libraries will include those libraries in the source distribution
and each of those libraries will have their own configure scripts
including the config.guess and config.sub files.
--
Earnie
___
config-patches
; http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD
>
these two links.
> If the version you run (./config.guess) is already up to date, please
> send the following data and any information you think might be
It isn't "al
replace *all* occurrences of config.guess and config.sub
in the source directories with the newest version from the repository.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
out a compiler???
>
He didn't say they didn't have a compiler, he said "do not have a *C*
compiler". The purpose of config.guess and config.sub is to identify a
default system and give an identifiable triplet string. A compiler
shouldn't need to be used to do that.
>> They can, however,
he "multilib" issue either; the only option for that is
--host and --build options. And you would need to set the CC variable
of course outside of configure.
Another option that I've employed in the past is to create a cc script
that DTRT regardless of uname.
executing a 32bit binary in a 64bit world where the OS adjusts for the
32bits in its 64bitness. The idea is that specifying the --host and
--build to be the same triplet the configure would execute the resulting
binary in tests and the compiler choice would be based on the --host
triplet.
>
> But in
MSK Toolkit the -s should be
Windows_NT. This doesn't match the newer WSL either from what I've found.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
l QNX SDP on a Linux, macOS, or Windows development host"[1]
> The next question is, what triplet should be output?
>
x86*-unknown-qnx
The -s for other hosts for this tool would match the development host
--
Earnie
[1]
http://www.qnx.com/developers/docs/7.0.0/#com.qnx.doc.qnxsdp.qui
https://savannah.gnu.org/projects/config and
http://git.savannah.gnu.org/gitweb/?p=config.git;a=summary.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
UNAME_RELEASE = 3.14.79-25-ARCH
> UNAME_SYSTEM = Linux
> UNAME_VERSION = #1 SMP PREEMPT Fri Jun 2 20:10:11 MDT 2017
> configure: error: cannot guess build type; you must specify one
>
> --
> Ulf Griesmann \\ tel: +1 301 339 4962
> 16833 Westbourne Terrace \\
in/arch =
> /usr/bin/oslevel =
> /usr/convex/getsysinfo =
>
> UNAME_MACHINE = aarch64
> UNAME_RELEASE = 3.10.102
> UNAME_SYSTEM = Linux
> UNAME_VERSION = #115 SMP PREEMPT Sat Dec 3 09:19:19 CST 2016
>
--
Earnie
> /bin/uname -X =
>
> hostinfo =
> /bin/universe =
> /usr/bin/arch -k =
>
> /bin/arch = x86_64
> /usr/bin/oslevel =
> /usr/convex/getsysinfo =
>
> UNAME_MACHINE = x86_64
> UNAME_RELEASE = 2.7.0(0.306/5/3)
>
tely this option isn't documented so it took some time to
> figure that out. It would be nice if thise were documented at the front
> of config.guess.
>
The --build, --host, --target options are configure options which cause
config.guess to not be executed. They are documented with
ackage providing config scripts. You can replace them with the
newer versions directly. You may run into issues with being able to
properly build and/or execute the package because it may not conform to
your system but that is a different issue.
[1] http://savannah.gnu.org/projects/config
--
Earni
On 6/5/2017 7:48 PM, Casey Leedom wrote:
> config.guess timestamp = 2005-08-03
Did your system type exist in 2005-08-03? You need to update the
scripts from the repository.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
ht
win issue. You need to take your issue to
cyg...@cygwin.com after review the FAQ at the http://cygwin.com website.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
> ===
> ./configure --enable-shared
>
> config.guess timestamp = 2014-11-04
>
Replace every config.guess and config.sub in the source file tree with
current ones from the config git repository.
https://savannah.gnu.org/git/?group=config
--
Earnie
__
i*:windows32*:*)
>i*:Windows_NT*:*|Pentium*:Windows_NT*:*)
>p*:CYGWIN*:*) (matched PPC)
>*:Interix*:*)
>
> Thoughts?
As far as MinGW is concerned I have no problems with removing these.
You didn't list 8664:Windows_NT:*), I'm okay with that one too.
--
Earnie
___
e/config-guess.data: Remove relevant test cases.
>
Now we wait to see who complains.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
fig.guess and config.sub with the most
current version from the repository at
http://savannah.gnu.org/git/?group=config.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
o create a mingw32 directory instead.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
blem. For any query you can
> reach back to me.
>
Replace all files named config.guess and config.sub with the current
ones from the repository.
--
HTH,
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
mestamp = 2018-08-02
>
> uname -m = x86_64
> uname -r = 2.10.0(0.325/5/3)
> uname -s = MINGW64_NT-10.0
> uname -v = 2018-06-13 23:34
>
You need to specify the --build=x86_64-w64-mingw32 triplet yourself.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
iles to the newest
versions found in the repository[1]. Be sure to replace all versions of
the files within the source directories.
[1] http://git.savannah.gnu.org/gitweb/?p=config.git;a=tree
--
Earnie
___
config-patches mailing list
config-pat
h named files in your source directories.
[1] http://savannah.gnu.org/projects/config
[2] http://savannah.gnu.org/git/?group=config
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
Why does config.guess return *-unknown-cygwin when `gcc -dumpmachine`
prints *-pc-cygwin? Am I wrong in thinking the two should match? There
is no *-unknown-cygwin-gcc on PATH but there is a *-pc-cygwin-gcc on PATH.
--
Earnie
___
config-patches
On 10/22/2018 4:16 PM, Ben Elliston wrote:
> On Mon, Oct 22, 2018 at 10:25:29AM -0400, Earnie wrote:
>
>> Why does config.guess return *-unknown-cygwin when `gcc
>> -dumpmachine` prints *-pc-cygwin? Am I wrong in thinking the two
>> should match? There is no *-un
to the locations present in the SPEC2006
source directory. Make sure you overwrite every config.guess and
config.sub with the newest versions.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config
points out
config.guess guesses the correct build system.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
building.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
, but certainly makes sense for
whatever odd shell you have.
The question that needs answered is what issue was being resolved by the
addition of the -r? The resolution here may need filters based on the
build host.
--
Earnie
___
config-patches
? Without that
information, it's hard to decide what this is all about.
I remember it being discussed but I don't remember the details and won't
do the research for you. In the end it was decided that using anything
other than uname -m to determine the system was a no go.
that such systems are just wrong.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
} files from
https://www.gnu.org/software/config in your project directories.
--
Earnie
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
used. I know
you mean for the variable to be set at autoreconf/configure usage but
there are always idiots who install it into their .profile files and
forget they did that.
--
Earnie
-- https://sites.google.com/site/earnieboyd
___
config-patches
where to find it.
--
Earnie
-- https://sites.google.com/site/earnieboyd
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches
and configure would execute the config.guess and config.sub in
that directory or error if the files do not exist or are unreadable.
--
Earnie
-- https://sites.google.com/site/earnieboyd
___
config-patches mailing list
config-patches@gnu.org
https
Minimal patch attached which provides a default of i686-pc instead of
i386-pc. This patch is important because of
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56909.
--
Earnie
-- https://sites.google.com/site/earnieboyd
gnuconfig-2013-08-09.patch
Description: Binary data
version of the config scripts from
ftp://ftp.gnu.org/pub/gnu/config/
Did you download the most current and replace the config.guess and
config.sub in the package? 2002 is 11 years plus old; did Windows 7
exist?
--
Earnie
-- https://sites.google.com/site/earnieboyd
40 matches
Mail list logo
