On Tue, Oct 23, 2007 at 11:23:31AM +0300, Timo Savola wrote:
> On Mon, 2007-10-22 at 20:25 -0700, Diane Holt wrote:
>
> > Actually, can you just tell me what --sbox-call is for? Looking at the
> > patch for it, it seems to just be skipping it anyway (unless I'm
> > missing something). The comment
nd for this problem?
You can try to override the c-library being used by setting an
SBALIEN_LIBRARY_PATH environment variable pointing to c libraries
needed by the toolchain (and secondarily to
/scratchbox/host_shared/lib). If this doesn't help, updating sb to
etch glibc will probably do.
--
can start the scratchbox with command:
# /scratchbox/sbin/sbox_ctl start
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
ourhosttarget: ~] > getent passwd mplourde
should work, and if the perl is not broken, then
[sbox-yourhosttarget: ~] > perl -e '@_=getpwnam("mplourde"); print "$_[2]\n"'
should work also.
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
_
ifferent versions
(0.7.0, 0.8.0, 0.8.1) of qemu or sbrsh cpu-transparency method.
One relatively easy way to check some of the qemu functionality is to
try to run env-tests against your target (run.sh in
scratchbox/tests/env in source tree; run from outside the scratchbox).
--
Toni Timonen
040-5
ssle with the the actual compilation
of the packages; almost as compiling natively.
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
^^^
> dh_clean: command returned error code
That error sounds like that in your compiler configuration
(arm-linux-gnueabi.conf) you have the default values made by
create_toolchain_conf.py.
A line like:
COMPILER_PACKAGE = "
Replace it with a valid debian package name like
COMPILER_PACKAGE
ODULES
It means that the definitition of PKG_CHECK_MODULES is
underquoted. Newer versions of autotools want the function names
properly quoted, so, instead of saying:
AC_DEFUN(PKG_CHECK_MODULES, [
The definition should go as:
AC_DEFUN([PKG_CHECK_MODULES], [
But this has no effect to anything in
ke-1.4/work/main.d/automake-1.4-p6$ touch -r . *
It looks like the sb-core build system needs a patch similar to
http://www.scratchbox.org/cgi-bin/darcsweb.cgi?r=1.0/sb-doctools-devkit;a=commitdiff;h=20060615110857-2603f-8600240ff6203e07214a903b14a9c0dfd9188
might be helpful, especially
http://www.scratchbox.org/wiki/Sbox102Maemo
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
or this to work, use SB Apophis.
Alternatively you can compile the tool inside the scratchbox using host
target.
> I am using scatchbox-0.9.8 since nokia's 770 stuff requires this
> version...
It works with Apophis too.
--
Toni Timonen
tside
> sbox).
> Can you give a hint what to do?
You can suid the binary outside the scratchbox, eg.
chown root:root ./foo
chmod +s ./foo
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scratchbox-
it no core is generated (ulimit -c unlimited is set). Adding a
> couple of printf's shows that it does abort execution at the null
> pointer dereference.
hmm.. atleast with sbrsh you have to set environment variable
SBOX_RLIMIT_CORE=unlimited, to get core files generated.
--
Toni
uot;, "credits" or "license" for more information.
> >>>
>
> I have compiled an ARM python and installed in the /targets/test1
> directoy. I guess the ARM python caused this problem. what is the
> root cause?
It might be, that the host python uses wrong module
completeness,
Mostly just for completeness.
They can also used to build cs toolchains using the old way with
sb-toolchains repository (arm-gcc3.4.cs2005q3-2-glibc.conf).
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
s
> files?
Those are done in the Building auxiliary tools step, more precisely
the actual generation steps are done in
sb-toolchain-extras/toolchain/post-install -phase.
See
http://scratchbox.org/cgi-bin/darcsweb.cgi?r=1.0/sb-toolchain-extras;a=headblob;f=/toolchain/post-install/Makefile
on how the toolchain is linked, the toolchain_conf -helper
might give some different suggestions outside the scratchbox than
inside; if configuration doesn't seem sane, you might want to try
running it outside.
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
__
asiest to reset the target and install them
to the clean target.
sb-conf reset --force
sb-conf install -edF
dpkg -i /scratchbox/compilers/`sb-conf sh -c`/packages/*.deb
If hello.c doesn't work even now, then there is something wrong elsewhere.
--
Toni Timonen
040-5111863,GPG 0x798
cket explicitly in
commandline:
$ /scratchbox/login env SSH_AUTH_SOCK=$SSH_AUTH_SOCK bash -l
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
y, I have tried to compile hello-world again and I
> have problems
>
> --
You probably installed a version of libc6 (or libc6-dev) that is
incompatible with the toolchain you are using. You should use the
libc6/libc6-dev packages p
om $SUBDIR/compiler-name.
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
utside
the scratchbox, you still need the /scratchbox symlink.
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
nstalled.
%2. Your normal user account must have write access to the
% /scratchbox/compilers directory and all directories under
% /scratchbox/device_tools.
%3. <>
That is, you have to chown those directories to yourself or give write
access otherwise.
--
Toni
scratchbox debian repository[2] in your
apt-sources, the packages might have been upgraded with a
dist-upgrade and that might cause the scratchbox to be turned off.
Footnotes:
[1] http://scratchbox.org/news/2006-03-31.html
[2] deb http://scratchbox.org/debian/ ./
but well, there could be a better hint:
http://bugzilla.scratchbox.org/bugzilla/show_bug.cgi?id=261
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin
On Thu, Mar 30, 2006 at 01:05:29PM +0200, Murray Cumming wrote:
> On Thu, 2006-03-30 at 13:28 +0300, Toni Timonen wrote:
> > On Thu, Mar 30, 2006 at 11:58:10AM +0200, Murray Cumming wrote:
> >
> > > When I try to then start (with
> > > sbox-config -st)
> >
On Thu, Mar 30, 2006 at 11:58:10AM +0200, Murray Cumming wrote:
> When I try to then start (with
> sbox-config -st)
Don't.
sbox-config --help | grep start
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
> > -Have multiple terminals open for the same target
>
> How might I do that?
1. open terminal
2. run '/scratcbox/login'
3. open an other terminal
4. run '/scratcbox/login'
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
targets open in the same scratchbox in the
same user. But you can:
-Have multiple terminals open for the same target
-Have multiple users in the scratchbox, each having separate targets.
-Have multiple different scratchboxes installed (as of 1.0.2), each of
them having different environments.
-
t;/scratchbox/host_shared/lib/ld.so: bad ELF interpreter: No such file or
>directory
Have you installed scratchbox to /scratchbox? Cross-compilers can't be
used from outside the scratchbox if the scratchbox is installed to to
a different location (at least you need a symlink /scratc
e.
Footnotes:
[1] http://www.scratchbox.org/wiki/HostDistributions
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
; 1.0.3 to see if my foreign toolchain works with it?
There is an experimental version of the wrapper available in the
1.0/scratchbox repository. You also need the newest
scratchbox-redirector (and updated qemu/sbrsh) from the repository to
get things working.
--
Toni Timonen
040-5111863,GPG 0x7984A4
ever I donot know how to resolve this issue. Can someone please
> help me out with this?
Wiki is somewhat ahead of time, because the alien toolchain wrapper is
going to be released in sb 1.0.3.
> I even tried executing the cross tools in my
> toolchain by using abso
2-branch from
the source repository.
>dpkg-buildpackage: source version is 5.5-1
>dpkg-checkbuilddeps: Unmet build dependencies: libgpmg1-dev (>= 1.19.6-20)
> quilt (>= 0.40-1)
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratch
e is glib compiled, no glibc.
If you are using toolchain compiled against glibc-2.3.2, you should already
have a ready-made glibc debian-packages available in
/scratchbox/compilers/arm-.../packages/
Footnotes:
[1] http://www.scratchbox.org/documentation/docbook/tutorial.ht
rminated due to an error: the dialog-like program exited
> with code 3 (was passed to it as the DIALOG_ERROR environment variable)
>
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
; /scratchbox/dev/null
If the previous command works, then this should work too. If not,
there might be some strange redirections in your environment.
[sbox-HOST: ~] > echo foo > /dev/null
If the above works, but this fails, the /dev in your sb target refers
to wrong place.
--
Toni
than /scratchbook right from the start?
To install to an other location from debs you can first make the symlink, eg.
ln -s /foo/bar/scratchbox /scratchbox
and then apt-get install the packages.
Alternatively you can just extract the tar.gz packages to an arbitrary
location and use them fr
at should be used is
/scratchbox/compilers/arm-gcc-3.3.2-uclibc-snapshot-20040229/arm-linux-uclibc/include/bits/atomicity.h
(re)moving the invalid ones away should help.
--
Toni Timonen
040-5111863,GPG 0x7984A4FD
___
Scratchbox-users mailing list
Scrat
e this, you
can either run 'make KERNEL_DIR=/foo/bar' or use SBOX_UNAME_RELEASE
environment variable to refer to target kernel (see
EnvironmentVariables[1] from wiki or variables.txt[2] from your sb
installation)
Footnotes:
[1] http://scratchbox.org/wiki/EnvironmentVariables
[2
On Sat, Nov 26, 2005 at 01:29:00PM +0800, wrote:
> I'm a newbie.i want compile the kernel in the scratchbox.what
> i should notice?
See kernel page from wiki.
http://scratchbox.org/wiki/Kernel
--
Toni Timonen
040-5111863,GPG
41 matches
Mail list logo
