g :)
(*) gpe-calendar only seems to control alarms while it's running.
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH7Ajo65uO8u5kvxoRAjuwAJ9aF2EbtXDUby+LpLLnFVUnUH4twACeNVPI
Wvy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Igo wrote:
| What do I need to do in order to put the device to sleep and have it
| wake up at a pre-determined time?
I thought others might be interested in the answer. It turns out that
putting values into
/sys/class/rtc/rtc0/alarm/[pending
figure out why each failed.
Since others obviously know how to build python packages for the various
supported architecures, I'm hoping that I can at least get a nudge in
the right direction. Again, I'm willing to do the work to document the
required steps.
Thanks!
- --
Bob Igo
won't need to give me a fish and
feed me for a day :)
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH/k+M65uO8u5kvxoRAlamAJ4kJm+w5LRLq9kzMZ5qFHSLJljasQCfelX
hat change yield the same error. Do I need to do the equivalent
of a 'make clean' before that works? Even if I get the override
working, I'm willing to help fix the problem in the build system, too,
as a way of giving back.
Please let me know what I can do to get past this. Thanks!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Igo wrote:
| Encouraged that it _should_ work, I tried again from scratch and got as
| far as this error while trying to build python-mysqldb:
| http://www.openembedded.org/the-q-a-team-strikes-back
|
| That page suggests two courses of action. I
for the system on which
the build is being done, which may be of a different version than the
headers for the version of the binary being built for the embedded
platform, but I just wanted to make sure I understood the goal before
going further.
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATU
plus the
added problem of a 'qemu-arm' process stuck at 100% CPU (one core) that
can't be killed by my regular user account or root. A build I did a few
months ago went just fine, so I'm not sure what changed.
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: GnuPG v
built python-pexpect for the hx4700 (or
the same CPU) that could send a copy to me? Or maybe there's a way to
revert the sources to how they were a month or two ago before the build
problem was introduced?
My local.conf and source-me.txt follow, in case it matters, but they're
pretty stand
12 and the latest
updates.
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIiJIo65uO8u5kvxoRAvJAAJ9Fr8heE1+L7Pb+YuDfFTYybzkHvwCfTatA
S2qe9I3TZjV/7eXN73Rlil0=
=15hG
-END PGP
le OE build instructions were
99% simpler, and 100% painless, when compared with the official build
instructions: http://blog.leggewie.org/?p=39 It's the only way I've
been able to build Angstrom.
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
, and the current generic build process should be a fallback
in case the official process fails or won't run on a user's distro of
choice. I mean, look at it - it's 5 shell commands, and then you're up
and running.
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Ver
x27;t figure out every problem in a
> reasonable amount of time, but it does help to have some record of where
> problems are so we can try and reproduce the problem and fix it.
I agree, and the problems I had are in the IRC logs and the email logs.
- --
Bob Igo
StormLogic
-BEGIN PGP SI
ild process. If the official build
process met everyone's needs, then that wouldn't be the case. Rolf's
build process has been shown to work when the official process does not.
How does it cause harm to anyone or anything to mention it in official
documentation and add that the Angstro
blems. I just seem to be the
only one representing those who did in this discussion.
> What happens if you follow the current instructions in
> http://www.angstrom-distribution.org/building-angstrom ? Is it still
> broken?
I'll try this on a spare machine and let you know.
- --
Bob
d be used based on how frequently each version appears in
the instructions. So which version should I use?
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI1nfq65uO8u5kvxoRArK+AJ42MD/b17juwV
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Koen Kooi wrote:
>> Either should be fine.
I appreciate you telling me that, but shouldn't the official build
instructions be corrected to show a consistent version?
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Koen Kooi wrote:
> Bob Igo wrote:
> Koen Kooi wrote:
> I appreciate you telling me that, but shouldn't the official build
> instructions be corrected to show a consistent version?
>
>> They already have been :)
Nearly :)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Koen Kooi wrote:
> Indeed there is. Fixed! Thanks for spotting it. It works on my machine
> because that those have both a 1.8.8 and 1.8.10 dir
No problem :) These are exactly the types of things I'd like to discover.
- --
Bob Igo
ssume it does for now and try
to continue. (I know I solved this before, but I don't have my old
build tree.) I would also recommend making the Angstrom-specific
local.conf a downloadable file or build it into the repo.
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: Gnu
p, why not emphasize that the first command is
done as root, but the remainder should be done as the regular user?
I'd also add a chown command:
As root:
==
mkdir /OE
chown -fR /OE [your_regular_user_name]
As your regular user:
==
cd /OE
tar zxf /OE/bitbake-1.8.10.tar.gz
etc.
- --
Bob
xactly this way.
I think that'd be fine, too, as long as the guide and included scripts
reflect that shift.
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI1r4V65uO8u5kvx
bxrender-1_0.9.2-r1: task do_compile: completed
NOTE: package libxrender-0.9.2: completed
NOTE: Tasks Summary: Attempted 521 tasks of which 520 didn't need to be
rerun and 1 failed.
ERROR:
'/OE/org.openembedded.stable/packages/fontconfig/fontconfig_2.4.1.bb' failed
- --
Bob Igo
StormL
d to the stable branch so that others don't run into that same
problem?
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI17mr65uO8u5kvxoRAma8AJ4tz1Q53Znon7zMVXEp2+IS0EYECwCeL1zY
zdE
TE: 1:
/OE/org.openembedded.stable/packages/gpe-session-scripts/gpe-session-scripts_0.67.bb,
do_qa_configure (17456)
NOTE: package gpe-session-scripts-0.67-r10: task do_qa_configure: completed
NOTE: package gpe-session-scripts-0.67: completed
NOTE: Tasks Summary: Attempted 2344 tasks of which 2340
E: package gpe-package-0.4-r0: task do_install: completed
NOTE: package gpe-package-0.4: completed
NOTE: Tasks Summary: Attempted 2381 tasks of which 2373 didn't need to
be rerun and 1 failed.
ERROR: '/OE/org.openembedded.stable/packages/bluez/bluez-gnome_0.14.bb'
failed
- --
Bo
g
Angstrom anymore, at least not in his latest release.
How can we make this build process work?
- --
Bob Igo
StormLogic
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI5Byi65uO8u5kvxoRAlENAJ9kcsMEOeNN5ejUAr1paysALi
27 matches
Mail list logo
