Re: [PATCH] Import config.sub and config.guess from upstream.
On 05/13/2016 01:55 AM, Jakub Sejdak wrote: +2016-05-13 Jakub Sejdak +* config.guess: Import version 2016-04-02 (newest). +* config.sub: Import version 2016-05-10 (newest). Installed on the trunk. I think this was NAK's for the release branches. jeff
Re: [PATCH] Import config.sub and config.guess from upstream.
Ping. 2016-05-14 13:36 GMT+02:00 Jakub Sejdak : > So please confirm that this is OK for trunk only and apply it. > Then I will start working on backporting this for other branches. > > 2016-05-14 11:29 GMT+02:00 Mike Stump : >> On May 14, 2016, at 1:15 AM, Jakub Sejdak wrote: >>> Then when those scripts get copied 'as they are' from GNU config? Only >>> for newly created branches? >> >> Only for trunk...
Re: [PATCH] Import config.sub and config.guess from upstream.
So please confirm that this is OK for trunk only and apply it. Then I will start working on backporting this for other branches. 2016-05-14 11:29 GMT+02:00 Mike Stump : > On May 14, 2016, at 1:15 AM, Jakub Sejdak wrote: >> Then when those scripts get copied 'as they are' from GNU config? Only >> for newly created branches? > > Only for trunk...
Re: [PATCH] Import config.sub and config.guess from upstream.
On May 14, 2016, at 1:15 AM, Jakub Sejdak wrote: > Then when those scripts get copied 'as they are' from GNU config? Only > for newly created branches? Only for trunk...
Re: [PATCH] Import config.sub and config.guess from upstream.
OK so just one final question to be clear: This patch was created from trunk with config,sub and config.guess copied from GNU config upstream. If you say, that I should just modify bits for my port, then this patch is still bad (since it modifies much more). Then when those scripts get copied 'as they are' from GNU config? Only for newly created branches? 2016-05-13 22:18 GMT+02:00 Mike Stump : > On May 13, 2016, at 11:50 AM, Jakub Sejdak wrote: >> >> OK I understand. So am I right, that in such a case there is no way to >> introduce new OS targets to branch 4.9 and 5? > > No. You just hand edit in the bits you need for your port, and seek approval > for that. > > In general, all new work goes into trunk, first. Once it is there, then you > can back port to the first oldest release branch. Once there, then you can > back port to the next oldest and so on. If it can't make it into a branch, > it can't go onto the next oldest branch. > > So, be be concrete, get 5 in first, then ask for 4.9. Get 6 in first, then > ask for 5. Get trunk in first, then ask for 6. > >> What about 6 branch and trunk? > > 6 would have the same answer as 4.9 and 5. For trunk, import from upstream > is the usual way to pick up that work. > >> On the other hand: this is my first patch and I'm not quite familiar >> with the procedure of applying patches to upstream. Who should upload >> my patch, when it gets accepted? > > Anyone with write access.
Re: [PATCH] Import config.sub and config.guess from upstream.
On May 13, 2016, at 11:50 AM, Jakub Sejdak wrote: > > OK I understand. So am I right, that in such a case there is no way to > introduce new OS targets to branch 4.9 and 5? No. You just hand edit in the bits you need for your port, and seek approval for that. In general, all new work goes into trunk, first. Once it is there, then you can back port to the first oldest release branch. Once there, then you can back port to the next oldest and so on. If it can't make it into a branch, it can't go onto the next oldest branch. So, be be concrete, get 5 in first, then ask for 4.9. Get 6 in first, then ask for 5. Get trunk in first, then ask for 6. > What about 6 branch and trunk? 6 would have the same answer as 4.9 and 5. For trunk, import from upstream is the usual way to pick up that work. > On the other hand: this is my first patch and I'm not quite familiar > with the procedure of applying patches to upstream. Who should upload > my patch, when it gets accepted? Anyone with write access.
Re: [PATCH] Import config.sub and config.guess from upstream.
OK I understand. So am I right, that in such a case there is no way to introduce new OS targets to branch 4.9 and 5? What about 6 branch and trunk? On the other hand: this is my first patch and I'm not quite familiar with the procedure of applying patches to upstream. Who should upload my patch, when it gets accepted? Thank you, Jakub 2016-05-13 20:03 GMT+02:00 Joseph Myers : > On Fri, 13 May 2016, Jakub Sejdak wrote: > >> Is it OK for trunk, gcc-4.9, gcc-5 and gcc-6 branches? > > It's not appropriate to update these scripts from upstream on release > branches. For example, config.guess changed a while back to output > x86_64-pc-linux-gnu in place of x86_64-unknown-linux-gnu, and clearly we > don't want to make such a change on 4.9 and 5 branches, which have > versions predating that change. > > -- > Joseph S. Myers > jos...@codesourcery.com
Re: [PATCH] Import config.sub and config.guess from upstream.
On Fri, 13 May 2016, Jakub Sejdak wrote: > Is it OK for trunk, gcc-4.9, gcc-5 and gcc-6 branches? It's not appropriate to update these scripts from upstream on release branches. For example, config.guess changed a while back to output x86_64-pc-linux-gnu in place of x86_64-unknown-linux-gnu, and clearly we don't want to make such a change on 4.9 and 5 branches, which have versions predating that change. -- Joseph S. Myers jos...@codesourcery.com
Re: [PATCH] Import config.sub and config.guess from upstream.
Is it OK for trunk, gcc-4.9, gcc-5 and gcc-6 branches?
2016-05-13 9:52 GMT+02:00 Jakub Sejdak :
> From: Kuba Sejdak
>
> ---
> ChangeLog| 4 +++
> config.guess | 93
>
> config.sub | 8 --
> 3 files changed, 59 insertions(+), 46 deletions(-)
>
> diff --git a/ChangeLog b/ChangeLog
> index eac1cc6..e092878 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,7 @@
> +2016-05-13 Jakub Sejdak
> +* config.guess: Import version 2016-04-02 (newest).
> +* config.sub: Import version 2016-05-10 (newest).
> +
> 2016-05-09 Aaron Sawdey
>
> * MAINTAINERS (Write After Approval): Add myself.
> diff --git a/config.guess b/config.guess
> index dcd5149..0967f2a 100755
> --- a/config.guess
> +++ b/config.guess
> @@ -2,7 +2,7 @@
> # Attempt to guess a canonical system name.
> # Copyright 1992-2016 Free Software Foundation, Inc.
>
> -timestamp='2016-01-01'
> +timestamp='2016-04-02'
>
> # This file is free software; you can redistribute it and/or modify it
> # under the terms of the GNU General Public License as published by
> @@ -237,6 +237,10 @@ case
> "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
> UNAME_MACHINE_ARCH=`arch | sed 's/OpenBSD.//'`
> echo ${UNAME_MACHINE_ARCH}-unknown-openbsd${UNAME_RELEASE}
> exit ;;
> +*:LibertyBSD:*:*)
> + UNAME_MACHINE_ARCH=`arch | sed 's/^.*BSD\.//'`
> + echo ${UNAME_MACHINE_ARCH}-unknown-libertybsd${UNAME_RELEASE}
> + exit ;;
> *:ekkoBSD:*:*)
> echo ${UNAME_MACHINE}-unknown-ekkobsd${UNAME_RELEASE}
> exit ;;
> @@ -268,42 +272,42 @@ case
> "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
> ALPHA_CPU_TYPE=`/usr/sbin/psrinfo -v | sed -n -e 's/^ The alpha
> \(.*\) processor.*$/\1/p' | head -n 1`
> case "$ALPHA_CPU_TYPE" in
> "EV4 (21064)")
> - UNAME_MACHINE="alpha" ;;
> + UNAME_MACHINE=alpha ;;
> "EV4.5 (21064)")
> - UNAME_MACHINE="alpha" ;;
> + UNAME_MACHINE=alpha ;;
> "LCA4 (21066/21068)")
> - UNAME_MACHINE="alpha" ;;
> + UNAME_MACHINE=alpha ;;
> "EV5 (21164)")
> - UNAME_MACHINE="alphaev5" ;;
> + UNAME_MACHINE=alphaev5 ;;
> "EV5.6 (21164A)")
> - UNAME_MACHINE="alphaev56" ;;
> + UNAME_MACHINE=alphaev56 ;;
> "EV5.6 (21164PC)")
> - UNAME_MACHINE="alphapca56" ;;
> + UNAME_MACHINE=alphapca56 ;;
> "EV5.7 (21164PC)")
> - UNAME_MACHINE="alphapca57" ;;
> + UNAME_MACHINE=alphapca57 ;;
> "EV6 (21264)")
> - UNAME_MACHINE="alphaev6" ;;
> + UNAME_MACHINE=alphaev6 ;;
> "EV6.7 (21264A)")
> - UNAME_MACHINE="alphaev67" ;;
> + UNAME_MACHINE=alphaev67 ;;
> "EV6.8CB (21264C)")
> - UNAME_MACHINE="alphaev68" ;;
> + UNAME_MACHINE=alphaev68 ;;
> "EV6.8AL (21264B)")
> - UNAME_MACHINE="alphaev68" ;;
> + UNAME_MACHINE=alphaev68 ;;
> "EV6.8CX (21264D)")
> - UNAME_MACHINE="alphaev68" ;;
> + UNAME_MACHINE=alphaev68 ;;
> "EV6.9A (21264/EV69A)")
> - UNAME_MACHINE="alphaev69" ;;
> + UNAME_MACHINE=alphaev69 ;;
> "EV7 (21364)")
> - UNAME_MACHINE="alphaev7" ;;
> + UNAME_MACHINE=alphaev7 ;;
> "EV7.9 (21364A)")
> - UNAME_MACHINE="alphaev79" ;;
> + UNAME_MACHINE=alphaev79 ;;
> esac
> # A Pn.n version is a patched version.
> # A Vn.n version is a released version.
> # A Tn.n version is a released field test version.
> # A Xn.n version is an unreleased experimental baselevel.
> # 1.2 uses "1.2" for uname -r.
> - echo ${UNAME_MACHINE}-dec-osf`echo ${UNAME_RELEASE} | sed -e
> 's/^[PVTX]//' | tr 'ABCDEFGHIJKLMNOPQRSTUVWXYZ' 'abcdefghijklmnopqrstuvwxyz'`
> + echo ${UNAME_MACHINE}-dec-osf`echo ${UNAME_RELEASE} | sed -e
> 's/^[PVTX]//' | tr ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz`
> # Reset EXIT trap before exiting to avoid spurious non-zero exit code.
> exitcode=$?
> trap '' 0
> @@ -376,16 +380,16 @@ case
> "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
> exit ;;
> i86pc:SunOS:5.*:* | i86xen:SunOS:5.*:*)
> eval $set_cc_for_build
> - SUN_ARCH="i386"
> + SUN_ARCH=i386
> # If there is a compiler, see if it is configured for 64-bit objects.
> # Note that the Sun cc does not turn __LP64__ into 1 like gcc does.
> # This test works for both compilers.
> - if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then
> + if [ "$CC_FOR_BUI
[PATCH] Import config.sub and config.guess from upstream.
From: Kuba Sejdak
---
ChangeLog| 4 +++
config.guess | 93
config.sub | 8 --
3 files changed, 59 insertions(+), 46 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index eac1cc6..e092878 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2016-05-13 Jakub Sejdak
+* config.guess: Import version 2016-04-02 (newest).
+* config.sub: Import version 2016-05-10 (newest).
+
2016-05-09 Aaron Sawdey
* MAINTAINERS (Write After Approval): Add myself.
diff --git a/config.guess b/config.guess
index dcd5149..0967f2a 100755
--- a/config.guess
+++ b/config.guess
@@ -2,7 +2,7 @@
# Attempt to guess a canonical system name.
# Copyright 1992-2016 Free Software Foundation, Inc.
-timestamp='2016-01-01'
+timestamp='2016-04-02'
# This file is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
@@ -237,6 +237,10 @@ case
"${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
UNAME_MACHINE_ARCH=`arch | sed 's/OpenBSD.//'`
echo ${UNAME_MACHINE_ARCH}-unknown-openbsd${UNAME_RELEASE}
exit ;;
+*:LibertyBSD:*:*)
+ UNAME_MACHINE_ARCH=`arch | sed 's/^.*BSD\.//'`
+ echo ${UNAME_MACHINE_ARCH}-unknown-libertybsd${UNAME_RELEASE}
+ exit ;;
*:ekkoBSD:*:*)
echo ${UNAME_MACHINE}-unknown-ekkobsd${UNAME_RELEASE}
exit ;;
@@ -268,42 +272,42 @@ case
"${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
ALPHA_CPU_TYPE=`/usr/sbin/psrinfo -v | sed -n -e 's/^ The alpha \(.*\)
processor.*$/\1/p' | head -n 1`
case "$ALPHA_CPU_TYPE" in
"EV4 (21064)")
- UNAME_MACHINE="alpha" ;;
+ UNAME_MACHINE=alpha ;;
"EV4.5 (21064)")
- UNAME_MACHINE="alpha" ;;
+ UNAME_MACHINE=alpha ;;
"LCA4 (21066/21068)")
- UNAME_MACHINE="alpha" ;;
+ UNAME_MACHINE=alpha ;;
"EV5 (21164)")
- UNAME_MACHINE="alphaev5" ;;
+ UNAME_MACHINE=alphaev5 ;;
"EV5.6 (21164A)")
- UNAME_MACHINE="alphaev56" ;;
+ UNAME_MACHINE=alphaev56 ;;
"EV5.6 (21164PC)")
- UNAME_MACHINE="alphapca56" ;;
+ UNAME_MACHINE=alphapca56 ;;
"EV5.7 (21164PC)")
- UNAME_MACHINE="alphapca57" ;;
+ UNAME_MACHINE=alphapca57 ;;
"EV6 (21264)")
- UNAME_MACHINE="alphaev6" ;;
+ UNAME_MACHINE=alphaev6 ;;
"EV6.7 (21264A)")
- UNAME_MACHINE="alphaev67" ;;
+ UNAME_MACHINE=alphaev67 ;;
"EV6.8CB (21264C)")
- UNAME_MACHINE="alphaev68" ;;
+ UNAME_MACHINE=alphaev68 ;;
"EV6.8AL (21264B)")
- UNAME_MACHINE="alphaev68" ;;
+ UNAME_MACHINE=alphaev68 ;;
"EV6.8CX (21264D)")
- UNAME_MACHINE="alphaev68" ;;
+ UNAME_MACHINE=alphaev68 ;;
"EV6.9A (21264/EV69A)")
- UNAME_MACHINE="alphaev69" ;;
+ UNAME_MACHINE=alphaev69 ;;
"EV7 (21364)")
- UNAME_MACHINE="alphaev7" ;;
+ UNAME_MACHINE=alphaev7 ;;
"EV7.9 (21364A)")
- UNAME_MACHINE="alphaev79" ;;
+ UNAME_MACHINE=alphaev79 ;;
esac
# A Pn.n version is a patched version.
# A Vn.n version is a released version.
# A Tn.n version is a released field test version.
# A Xn.n version is an unreleased experimental baselevel.
# 1.2 uses "1.2" for uname -r.
- echo ${UNAME_MACHINE}-dec-osf`echo ${UNAME_RELEASE} | sed -e
's/^[PVTX]//' | tr 'ABCDEFGHIJKLMNOPQRSTUVWXYZ' 'abcdefghijklmnopqrstuvwxyz'`
+ echo ${UNAME_MACHINE}-dec-osf`echo ${UNAME_RELEASE} | sed -e
's/^[PVTX]//' | tr ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz`
# Reset EXIT trap before exiting to avoid spurious non-zero exit code.
exitcode=$?
trap '' 0
@@ -376,16 +380,16 @@ case
"${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
exit ;;
i86pc:SunOS:5.*:* | i86xen:SunOS:5.*:*)
eval $set_cc_for_build
- SUN_ARCH="i386"
+ SUN_ARCH=i386
# If there is a compiler, see if it is configured for 64-bit objects.
# Note that the Sun cc does not turn __LP64__ into 1 like gcc does.
# This test works for both compilers.
- if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then
+ if [ "$CC_FOR_BUILD" != no_compiler_found ]; then
if (echo '#ifdef __amd64'; echo IS_64BIT_ARCH; echo '#endif') | \
- (CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) | \
+ (CCOPTS="" $CC_FOR_BUILD -E - 2>/dev/null) | \
grep IS_64BIT_ARCH >/dev/null
then
- SUN_ARCH="x86_64"
