From: Ormund Williams <ormundw@panix.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/directfb
Date: Thu, 09 Oct 2008 08:42:22 -0400 [thread overview]
Message-ID: <1223556143.3276.82.camel@localhost.localdomain> (raw)
In-Reply-To: <d6cda7730810082221w6019c604occa5158abac583f2@mail.gmail.com>
On Thu, 2008-10-09 at 02:21 -0300, Thiago A. Corr?a wrote:
> I have no idea what directfb-csource is.
It's a utility for converting a PNG file to a c source file. The source
code for it is in the DirectFB source itself.
> This just works for me when compiling for AVR32.
>
> I also don't have it on my search path either:
> localhost directfb # which directfb-csource
> which: no directfb-csource in
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.2:/usr/kde/4.0/sbin:/usr/kde/4.0/bin)
>
> So It can't be coming from the host. Did it work at all before?
> Perhaps it's one of the new options?
>
I'm using a make file I hacked together based on one Peter Korsgaard
posted to the list some time ago. Under this make file it's built and
has the target prefix attached, i686-linux-directfb-csource under
the ../staging_dir/usr/bin
This is puzzling.
Regards
__
Ormund
next prev parent reply other threads:[~2008-10-09 12:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 20:29 [Buildroot] svn commit: trunk/buildroot/package/directfb correa at uclibc.org
2008-10-08 18:36 ` Peter Korsgaard
2008-10-09 5:06 ` Thiago A. Corrêa
2008-10-09 7:57 ` Bernhard Reutner-Fischer
2008-10-09 1:25 ` Ormund Williams
2008-10-09 5:21 ` Thiago A. Corrêa
2008-10-09 12:42 ` Ormund Williams [this message]
2008-10-09 12:51 ` Peter Korsgaard
2008-10-09 13:11 ` Ormund Williams
2008-10-11 4:19 ` Ormund Williams
-- strict thread matches above, loose matches on Subject: below --
2009-01-21 19:20 jacmet at uclibc.org
2009-01-21 19:20 jacmet at uclibc.org
2009-01-21 15:49 jacmet at uclibc.org
2009-01-11 20:35 ulf at uclibc.org
2008-10-09 18:36 correa at uclibc.org
2008-10-09 18:36 correa at uclibc.org
2008-10-09 5:06 correa at uclibc.org
2008-10-09 9:45 ` Peter Korsgaard
2008-04-01 6:51 jacmet at uclibc.org
2007-11-16 16:10 vanokuten at uclibc.org
2007-09-12 5:20 ulf at uclibc.org
2007-09-05 6:49 ulf at uclibc.org
2007-08-13 6:14 ulf at uclibc.org
2007-08-12 23:30 ulf at uclibc.org
2007-08-12 18:21 ulf at uclibc.org
2007-08-12 14:40 ulf at uclibc.org
2007-08-11 21:53 ulf at uclibc.org
2007-06-26 6:24 aldot at uclibc.org
2007-02-02 12:41 jacmet at uclibc.org
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=1223556143.3276.82.camel@localhost.localdomain \
--to=ormundw@panix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.