Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Laird <daniel.j.laird@nxp.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package: games games/ace_of_penguins games/gnuch etc...
Date: Mon, 1 Sep 2008 02:06:45 -0700 (PDT)	[thread overview]
Message-ID: <19250901.post@talk.nabble.com> (raw)
In-Reply-To: <COL102-DS131551BA49AC350CABE3EFDC630@phx.gbl>


I have just tried to patch various games packages and java ones
jamvm (packages/java/jamvm) works fine patch-version and patch-version.arch
work

ace_of_penguins - the libtool patch fails I think this a fault with libtool
patch not the dir move
lxdoom - patch target works
rubix - patch target works
gnuchess - patch target works
vice - patch target works

So I think the move is fine and that the issues are with making the libtool
patch apply to more targets
Daniel Laird

-- 
View this message in context: http://www.nabble.com/svn-commit%3A-trunk-buildroot-package%3A-games-games-ace_of_penguins-games-gnuch-etc...-tp19219940p19250901.html
Sent from the BuildRoot mailing list archive at Nabble.com.

  reply	other threads:[~2008-09-01  9:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 13:27 [Buildroot] svn commit: trunk/buildroot/package: games games/ace_of_penguins games/gnuch etc laird at uclibc.org
2008-08-29 13:38 ` Hans-Christian Egtvedt
2008-08-29 13:52   ` Daniel Laird
2008-08-29 16:53   ` hartleys
2008-08-29 16:59     ` Daniel Laird
2008-08-29 18:16       ` danieljlaird at hotmail.com
2008-09-01  9:06         ` Daniel Laird [this message]
2008-09-02 17:49           ` hartleys
2008-09-02 18:15             ` [Buildroot] svn commit: trunk/buildroot/package: gamesgames/ace_of_penguins " hartleys
2008-09-03  6:59             ` [Buildroot] svn commit: trunk/buildroot/package: games games/ace_of_penguins " Peter Korsgaard
2008-09-03  7:03               ` Daniel Laird

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19250901.post@talk.nabble.com \
    --to=daniel.j.laird@nxp.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox