[Buildroot] [Bug 2965] New: Broken linkage to xkbcomp (blocking X server startup)

[Buildroot] [Bug 2965] New: Broken linkage to xkbcomp (blocking X server startup)

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=2965

           Summary: Broken linkage to xkbcomp (blocking X server startup)
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: adm at mpscompany.pl
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Hello,

Buildroot generates rootfs image with xkbcomp file is a sym link to host
xkbcomp binary.

[dynia at entropia images]$ tar tvf rootfs.tar | grep /usr/share/X11/xkb/xkbcomp
lrwxrwxrwx root/root         0 2010-12-14 20:24 ./usr/share/X11/xkb/xkbcomp ->
/mnt/b/Arm/buildroot-2010.11/output/host/usr/bin/xkbcomp

So in my case I got ARM rootfs link to non-existing and wrong (since x86)
binary.

Additionally I guest the xkbcomp is placed in a wrong dir since X server is
searching it in /usr/bin and the broken link is located in /usr/share/X11/xkb -
but this is rather a minor issue.

This have been tested on buildroot-2010.11 and daily snapshot at 15th Dec 2010.

Regards

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 2965] Broken linkage to xkbcomp (blocking X server startup)

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=2965

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at buildroot.uclibc |thomas.petazzoni at free-elect
                   |.org                        |rons.com

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 2965] Broken linkage to xkbcomp (blocking X server startup)

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=2965

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com>  ---
I'm sending in a minute a patch that fixes this to the Buildroot mailing-list.

The thing is that xkeyboard-config <= 1.8 created a symbolic link from
/usr/share/X11/xkb/xkbcomp to the xkbcomp binary used@compile time, which in
cross-compile mode in the host xkbcomp. In fact, this symbolic link seems to be
useless, and has been removed from xkeyboard-config >= 1.9. So the fix was to
just bump xkeyboard-config to the latest available version, 2.0.

Concerning the usr/bin/xkbcomp binary in the target directory, it is there,
since the xkeyboard-config package selects xapp_xkbcomp for the target. Here is
what I have here :

$ ls -l target/usr/share/X11/xkb/xkbcomp
ls: cannot access target/usr/share/X11/xkb/xkbcomp: No such file or directory

$ ls -l target/usr/bin/xkbcomp 
-rwxr-xr-x 1 test test 156804 Dec 22 09:27 target/usr/bin/xkbcomp

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Buildroot] [Bug 2965] Broken linkage to xkbcomp (blocking X server startup)

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=2965

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #2 from Peter Korsgaard <jacmet@uclibc.org>  ---
Fixed in git by Thomas, thanks.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.