Error installing LPCXpresso 8.2.2 under Fedora 26

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Error installing LPCXpresso 8.2.2 under Fedora 26

1,216 Views
idelsink
Contributor I

Hello,
I'm trying to install LPCXpresso 8.2.2 under fedora 26 but I get the following error:

$ No protocol specified
invalid command name "bind"
 while executing
"::unknown bind Text <Tab>"
 ("uplevel" body line 1)
 invoked from within
"uplevel 1 $next $args"
 (procedure "::obj::Unknown" line 3)
 invoked from within
"bind Text <Tab>"
 (procedure "::InstallJammer::InitializeGui" line 19)
 invoked from within
"::InstallJammer::InitializeGui "
 (procedure "::InstallJammer::InitInstall" line 68)
 invoked from within
"::InstallJammer::InitInstall"
 (file "/installkitvfs/main.tcl" line 39322)

 

I have installed all the listed dependency's in the INSTALL.txt file.

$ sudo dnf install gtk2.i686 glibc.i686 glibc-devel.i686 libstdc++.i686 zlib-devel.i686 ncurses-devel.i686 libX11-devel.i686 libXrender.i686 libXrandr.i686 libusb.i686 libXtst.i686 nss.i686 Last metadata expiration check: 0:00:00 ago on Mon 21 Aug 2017 10:40:19 AM CEST. Package gtk2-2.24.31-4.fc26.i686 is already installed, skipping. Package glibc-2.25-8.fc26.i686 is already installed, skipping. Package glibc-devel-2.25-8.fc26.i686 is already installed, skipping. Package libstdc++-7.1.1-3.fc26.i686 is already installed, skipping. Package zlib-devel-1.2.11-2.fc26.i686 is already installed, skipping. Package ncurses-devel-6.0-8.20170212.fc26.i686 is already installed, skipping. Package libX11-devel-1.6.5-2.fc26.i686 is already installed, skipping. Package libXrender-0.9.10-2.fc26.i686 is already installed, skipping. Package libXrandr-1.5.1-2.fc26.i686 is already installed, skipping. Package libusb-1:0.1.5-8.fc26.i686 is already installed, skipping. Package libXtst-1.2.3-2.fc26.i686 is already installed, skipping. Package nss-3.31.0-1.1.fc26.i686 is already installed, skipping. Dependencies resolved. Nothing to do. Complete!

The strace output looks can be viewed via the attachment.

Original Attachment has been moved to: log.txt.zip

0 Kudos
2 Replies

766 Views
lpcxpresso_supp
NXP Employee
NXP Employee

Thank you for your comments and feedback. I'm glad to see that you got up and running. 

 

Please be aware, that the old Code Red site is very out of date now. The latest LPCXpresso information for installing on Linux can be found in the Installation Guide, or else at Installing LPCXpresso on Linux 

 

As you may be aware though, the last LPCXpresso IDE release was made some time before Fedora 26 was released. However I've flagged your comments regarding Wayland in our system for consideration for the MCUXpresso IDE installer in the future (though note that we only provide an MCUXpresso IDE installer for Ubuntu, and have no plans currently for Centos/Fedora). For more informaton on MCUXpresso IDE, please visit : http://www.nxp.com/mcuxpresso/ide

 

Regards,

LPCXpresso Support

0 Kudos

766 Views
idelsink
Contributor I

The problem I'm having is that I use Fedora 26. This uses wayland.

So to install LPCXpresso I did the following:

  1. Logout 
  2. On the login screen select the "GNOME on Xorg" option (this makes sure to use X11 instead of wayland)
  3. Run the installer
  4. Edit the desktop entry for LPCXpresso (located under "/usr/local/share/applications/lpcxpresso-program.desktop")
    cp /usr/local/share/applications/lpcxpresso-program.desktop ~/.local/share/applications/
    Change "Exec=/usr/local/lpcxpresso_8.2.2_650/lpcxpresso/lpcxpresso" to "Exec=env GDK_BACKEND=x11 /usr/local/lpcxpresso_8.2.2_650/lpcxpresso/lpcxpresso"
    This makes sure that x11 is used by eclipse (see: Make applications (Eclipse) use x11 backend on Wayland (Fedora 25) | Coffee Oriented Programming )
  5. Logout and log back in using wayland

The problem now is solved for me.

In addition to the steps mentioned above I also ran the installation process of the following guide: RunningOnLinux - ** Code Red Support Site ** 

This doesn't mean that this issue in general is solved! This should all be done by default or by detection of the display server type (e.g. Wayland or X)

0 Kudos