* [Buildroot] problems and solutions for tinyx
@ 2006-07-24 4:25 Biucchi Gabriele
2006-07-24 10:23 ` [Buildroot] where to put patches for packages? Marc Lindahl
2006-07-24 11:12 ` [Buildroot] problems and solutions for tinyx Erik Andersen
0 siblings, 2 replies; 8+ messages in thread
From: Biucchi Gabriele @ 2006-07-24 4:25 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] where to put patches for packages?
2006-07-24 4:25 [Buildroot] problems and solutions for tinyx Biucchi Gabriele
@ 2006-07-24 10:23 ` Marc Lindahl
2006-07-24 11:08 ` Erik Andersen
2006-07-24 11:12 ` [Buildroot] problems and solutions for tinyx Erik Andersen
1 sibling, 1 reply; 8+ messages in thread
From: Marc Lindahl @ 2006-07-24 10:23 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] where to put patches for packages?
2006-07-24 10:23 ` [Buildroot] where to put patches for packages? Marc Lindahl
@ 2006-07-24 11:08 ` Erik Andersen
2006-07-24 11:19 ` Marc Lindahl
0 siblings, 1 reply; 8+ messages in thread
From: Erik Andersen @ 2006-07-24 11:08 UTC (permalink / raw)
To: buildroot
On Mon Jul 24, 2006 at 01:17:23PM -0400, Marc Lindahl wrote:
> 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--
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] problems and solutions for tinyx
2006-07-24 4:25 [Buildroot] problems and solutions for tinyx Biucchi Gabriele
2006-07-24 10:23 ` [Buildroot] where to put patches for packages? Marc Lindahl
@ 2006-07-24 11:12 ` Erik Andersen
2006-07-25 4:26 ` Biucchi Gabriele
1 sibling, 1 reply; 8+ messages in thread
From: Erik Andersen @ 2006-07-24 11:12 UTC (permalink / raw)
To: buildroot
On Mon Jul 24, 2006 at 01:22:58PM +0200, Biucchi Gabriele wrote:
> 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
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?
> 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.
> 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--
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] where to put patches for packages?
2006-07-24 11:08 ` Erik Andersen
@ 2006-07-24 11:19 ` Marc Lindahl
2006-07-24 11:26 ` Erik Andersen
0 siblings, 1 reply; 8+ messages in thread
From: Marc Lindahl @ 2006-07-24 11:19 UTC (permalink / raw)
To: buildroot
On Jul 24, 2006, at 2:07 PM, Erik Andersen wrote:
> On Mon Jul 24, 2006 at 01:17:23PM -0400, Marc Lindahl wrote:
>> 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.
Thanks.... so I assume that you can control the order as usual by
naming the patches 001-blahblah.patch 002-blah.patch etc.?
>
> -Erik
>
> --
> Erik B. Andersen http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] where to put patches for packages?
2006-07-24 11:19 ` Marc Lindahl
@ 2006-07-24 11:26 ` Erik Andersen
0 siblings, 0 replies; 8+ messages in thread
From: Erik Andersen @ 2006-07-24 11:26 UTC (permalink / raw)
To: buildroot
On Mon Jul 24, 2006 at 02:19:17PM -0400, Marc Lindahl wrote:
> 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--
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] problems and solutions for tinyx
2006-07-24 11:12 ` [Buildroot] problems and solutions for tinyx Erik Andersen
@ 2006-07-25 4:26 ` Biucchi Gabriele
2006-07-26 12:11 ` Erik Andersen
0 siblings, 1 reply; 8+ messages in thread
From: Biucchi Gabriele @ 2006-07-25 4:26 UTC (permalink / raw)
To: buildroot
Here is the patch for tinyx.mk
The change for tinyx-config.patch is not needed.
Best regards,
Gabriele
-------------- next part --------------
--- buildroot/package/tinyx/tinyx.mk 2006-07-25 11:56:45.000000000 +0200
+++ br/package/tinyx/tinyx.mk 2006-07-25 12:03:45.000000000 +0200
@@ -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:
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Buildroot] problems and solutions for tinyx
2006-07-25 4:26 ` Biucchi Gabriele
@ 2006-07-26 12:11 ` Erik Andersen
0 siblings, 0 replies; 8+ messages in thread
From: Erik Andersen @ 2006-07-26 12:11 UTC (permalink / raw)
To: buildroot
On Tue Jul 25, 2006 at 01:24:19PM +0200, Biucchi Gabriele wrote:
> 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--
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2006-07-26 12:11 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-24 4:25 [Buildroot] problems and solutions for tinyx Biucchi Gabriele
2006-07-24 10:23 ` [Buildroot] where to put patches for packages? Marc Lindahl
2006-07-24 11:08 ` Erik Andersen
2006-07-24 11:19 ` Marc Lindahl
2006-07-24 11:26 ` Erik Andersen
2006-07-24 11:12 ` [Buildroot] problems and solutions for tinyx Erik Andersen
2006-07-25 4:26 ` Biucchi Gabriele
2006-07-26 12:11 ` Erik Andersen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox