Re: [patch] config.sub recognize m68k-next-openstep as openstep not nextstep3

2019-03-28 Thread Ben Elliston
On Thu, Mar 28, 2019 at 10:11:08PM +0100, Urs Janßen wrote:

> ChangeLog:
> 2019-03-28  Urs Janßen 
>* config.sub recognize m68k-next-openstep* as openstep*, not nextstep3

It would be cool if you had updated the testsuite, given that you had
already developed the test cases.

Patch applied.

Ben


signature.asc
Description: PGP signature
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches


[patch] config.sub recognize m68k-next-openstep as openstep not nextstep3

2019-03-28 Thread Urs Janßen
Before the patch:
./config.sub.o m68k-next-openstep4
m68k-next-nextstep3  # <- this is wrong
./config.sub.o i386-next-openstep4
i386-next-openstep4
./config.sub.o m68k-next-nextstep3
m68k-next-nextstep3

After the patch:
./config.sub m68k-next-openstep4 
m68k-next-openstep4
./config.sub i386-next-openstep4 
i386-next-openstep4
./config.sub m68k-next-nextstep3
m68k-next-nextstep3

Comment:
I belive that *-next-openstep* is limited to *-next-openstep4 (config.guess
emmit 1 digit version number and starting with version 5 the os was renamed
to rhapsody) but I didn't "hardcode" that in the patch.

ChangeLog:
2019-03-28  Urs Janßen 
   * config.sub recognize m68k-next-openstep* as openstep*, not nextstep3
--- config.sub.o	2019-03-28 21:52:46.476144364 +0100
+++ config.sub	2019-03-28 21:55:53.506810964 +0100
@@ -822,7 +822,9 @@
 		cpu=m68k
 		vendor=next
 		case $os in
-		nextstep* )
+		openstep*)
+		;;
+		nextstep*)
 			;;
 		ns2*)
 		  os=nextstep2
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches


Re: lcm 1.1.2 install on NVIDIA Jetson TX2

2019-03-28 Thread Boris Borukhin
Hi Ben,
You are cirrect.
The vendor original name was "aarch64".
I have changed the uname to ARM to enable remote debugging from visual
studio with Jetson tx2.

after reverting to original uname, the installation is successful.

Thanks 

Boris


בתאריך יום ד׳, 27 במרץ 2019, 22:14, מאת Ben Elliston ‏:

> Hi Boris
>
> Thanks for your report.
>
> On Wed, Mar 27, 2019 at 04:01:26PM +, Boris Borukhin wrote:
>
> > uname -m = ARM
> > uname -r = 4.4.38-tegra
> > uname -s = Linux
> > uname -v = #1 SMP PREEMPT Wed Jun 6 07:57:23 CDT 2018
>
> Why does this Linux kernel report "ARM" in upper case instead of lower
> case, like everyone else? What a pain. I wish vendors wouldn't make
> unnecessary changes like this.
>
> Before we make the obvious change to recognise "ARM", can you please
> try and establish why this is so? Are you sure you're not running a
> patched kernel, or running an unintended version of unane? Perhaps
> check with "which uname"?
>
> Thanks,
> Ben
>
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches


Re: lcm 1.1.2 install on NVIDIA Jetson TX2

2019-03-28 Thread Ben Elliston
On Thu, Mar 28, 2019 at 08:13:52AM +0200, Boris Borukhin wrote:

> after reverting to original uname, the installation is successful.

Phew, I am glad. :)

Cheers,
Ben


signature.asc
Description: PGP signature
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches