Skip to contentSkip to conversation

problems and solutions for tinyx

Buildroot Applied Biucchi Gabriele 3 participants 8 messages Jul 24, 2006 – Jul 26, 2006

lore
Share & tools
lore
#0 lore raw

I want only to point out some problems I had with tinyx and the solutions that work with me: I hope, this can help somebody.

1) change in tinyx-config.patch

tinyx-config.patch starts with:

--- xc/config/cf/host.def~ 2005-04-02 14:51:31.000000000 -0700 +++ xc/config/cf/host.def 2005-04-26 01:22:00.000000000 -0600

but I think it should be:

--- xc-011010/config/cf/host.def~ 2005-04-02 14:51:31.000000000 -0700 +++ xc-011010/config/cf/host.def 2005-04-26 01:22:00.000000000 -0600

2) change in tinyx.mk

Some programs (like rxvt) need x-includes and x-libraries in $(STAGING_DIR)/usr/X11R6/ , but tinyx.mk does not install anything there.

A naif solution consists to copy everything from $(TINYX_DIR)/exports/ into $(STAGING_DIR)/usr/X11R6/, substituting the line

tinyx: zlib $(TINYX_LIBX)/libX11.so.6.2 $(TINYX_BINX)/Xfbdev

with the following lines (please note the "-L" option used with cp):

$(STAGING_DIR)/usr/X11R6/lib/libX11.so.6.2: $(TINYX_LIBX)/libX11.so.6.2

    mkdir -p $(STAGING_DIR)/usr/X11R6/lib
    mkdir -p $(STAGING_DIR)/usr/X11R6/include
    cp -fRL $(TINYX_DIR)/exports/include/* $(STAGING_DIR)/usr/X11R6/include/
    cp -fRL $(TINYX_DIR)/exports/lib/* $(STAGING_DIR)/usr/X11R6/lib/

tinyx: zlib $(TINYX_LIBX)/libX11.so.6.2 $(TINYX_BINX)/Xfbdev $(STAGING_DIR)/usr/X11R6/lib/libX11.so.6.2

3) another change in tinyx.mk

The $PATH variable includes "/usr/bin/X11", but there is nothing there. A solution is to create a symbolic link between "/usr/bin/X11" and "/usr/X11R6/bin", putting in the tinyx.mk the line

ln -s /usr/X11R6/bin $(TARGET_DIR)/usr/bin/X11

Best regards,
Gabriele

___________________________________________________________
Der fr?he Vogel f?ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de

#1 lore raw

[Buildroot] where to put patches for packages?

Hi,
I'm a relative newbie to buildroot... I'm trying to figure out where to put (non-kernel) patches to packages (e.g. pcmcia-cs)... can someone point it out to me?
Thx,
M

#2 lore raw

[Buildroot] where to put patches for packages?

Quoted 6 lines · Marc Lindahl

Hi,
I'm a relative newbie to buildroot... I'm trying to figure out where to put (non-kernel) patches to packages (e.g. pcmcia-cs)... can someone point it out to me?
Thx,
M

Packages have all their associated stuff in the
package/packagename/
directory. So for example pcmcia-cs lives under
package/pcmcia/
and anything matching buildroot/package/pcmcia/pcmcia\*.patch will be applied when building pcmcia-cs.

-Erik

--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

#3 lore raw

[Buildroot] where to put patches for packages?

Quoted 9 lines · Erik Andersen
Quoted 7 lines · Marc Lindahl

Hi,
I'm a relative newbie to buildroot... I'm trying to figure out where to
put (non-kernel) patches to packages (e.g. pcmcia-cs)... can someone point it out to me?
Thx,
M

Quoted 6 lines

Packages have all their associated stuff in the
package/packagename/
directory. So for example pcmcia-cs lives under
package/pcmcia/
and anything matching buildroot/package/pcmcia/pcmcia\*.patch will be applied when building pcmcia-cs.

Thanks.... so I assume that you can control the order as usual by naming the patches 001-blahblah.patch 002-blah.patch etc.?

Quoted 6 lines

-Erik

--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

#4 lore raw

[Buildroot] where to put patches for packages?

Quoted 2 lines · Marc Lindahl

Thanks.... so I assume that you can control the order as usual by naming the patches 001-blahblah.patch 002-blah.patch etc.?

precisely. So if the current package/pcmcia/pcmcia.patch patch needs to be renamed (or replaced entirely), that can of course be done easily enough.

-Erik

--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

#5 lore raw
In reply to Biucchi Gabriele

config/cf/host.def 2005-04-26 01:22:00.000000000 -0600

Quoted 14 lines · Biucchi Gabriele

I want only to point out some problems I had with tinyx and the solutions that work with me: I hope, this can help somebody.

1) change in tinyx-config.patch

tinyx-config.patch starts with:

config/cf/host.def 2005-04-26 01:22:00.000000000 -0600 renamed from config/cf/host.def~ 2005-04-02 14:51:31.000000000 -0700 +0 -0

but I think it should be:

config/cf/host.def 2005-04-26 01:22:00.000000000 -0600 renamed from config/cf/host.def~ 2005-04-02 14:51:31.000000000 -0700 +0 -0

Patches are applied using 'patch -p1' so regardless of what the leading path is, it should be getting stripped. Are you actually seeing a problem with this patch being applied?

Quoted 7 lines

2) change in tinyx.mk

Some programs (like rxvt) need x-includes and x-libraries in $(STAGING_DIR)/usr/X11R6/ , but tinyx.mk does not install anything there.

A naif solution consists to copy everything from $(TINYX_DIR)/exports/ into $(STAGING_DIR)/usr/X11R6/

This certainly seems to be Right Thing to do here.

Quoted 7 lines

3) another change in tinyx.mk

The $PATH variable includes "/usr/bin/X11", but there is nothing there. A solution is to create a symbolic link between "/usr/bin/X11" and "/usr/X11R6/bin", putting in the tinyx.mk the line

ln -s /usr/X11R6/bin $(TARGET_DIR)/usr/bin/X11

That seems best. Any chance you could make these changes and submit a patch implementing them.

-Erik

--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

#6 lore raw

Here is the patch for tinyx.mk

The change for tinyx-config.patch is not needed.

Best regards,
Gabriele

-------------- next part --------------

package/tinyx/tinyx.mk +12 -1
@@ -126,8 +126,19 @@
 		cp -pRf $$file $(TINYX_LIBX) ; \
 	done
 
-tinyx: zlib $(TINYX_LIBX)/libX11.so.6.2 $(TINYX_BINX)/Xfbdev
+#
+# Install x-includes and x-libraries in $(STAGING_DIR)/usr/X11R6/
+# and add a symbolic link between /usr/bin/X11 and /usr/X11R6/bin
+#
+$(STAGING_DIR)/usr/X11R6/lib/libX11.so.6.2: $(TINYX_LIBX)/libX11.so.6.2
+	mkdir -p $(STAGING_DIR)/usr/X11R6/lib
+	mkdir -p $(STAGING_DIR)/usr/X11R6/include
+	cp -fRL $(TINYX_DIR)/exports/include/* $(STAGING_DIR)/usr/X11R6/include/
+	cp -fRL $(TINYX_DIR)/exports/lib/* $(STAGING_DIR)/usr/X11R6/lib/
+	ln -s /usr/X11R6/bin $(TARGET_DIR)/usr/bin/X11
 
+tinyx: zlib $(TINYX_LIBX)/libX11.so.6.2 $(TINYX_BINX)/Xfbdev $(STAGING_DIR)/usr/X11R6/lib/libX11.so.6.2 
+	    
 tinyx-source: $(DL_DIR)/$(TINYX_SOURCE)
 
 tinyx-clean:
#7 lore raw
Quoted 3 lines · Biucchi Gabriele

Here is the patch for tinyx.mk

The change for tinyx-config.patch is not needed.

applied, thx.

-Erik

--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--