On 09/10/2012 09:30 PM, Max E. Reyes Vera J. wrote:
I'm trying to run sb2-init but I'm getting the error:
"checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details."
You're compiling libtool whilst creating a t
On 04/05/2012 04:01 PM, Athanasios Silis wrote:
what files do you think are missing? cause after I completed your
sb-conf steps, i get pretty much the same output as before:
I was thinking you're missing the base etc files, and files related the
debian infrastructure.
you probably meant "s
On 04/05/2012 11:26 AM, Athanasios Silis wrote:
my sbox has an arguably very old toolchain. here/s the info:
[sbox-sbc26: ~] > sb-conf sh
Compiler: arm-linux-gcc3.4.cs-glibc2.3
Devkits: perl autotools-legacy git python-legacy qemu svn debian-squeeze
CPU-transparency: /scratchbox/devkits/qemu/bin
On 03/28/2012 03:02 PM, James Brown wrote:
Thanks for your answer. It is very pitty.
Indeed it is.
Some of the packages are still generated inside Scratchbox itself. It
could do with an upgrade to the packaging tools.
After that, it would probably be reasonable at one point to have better,
On 03/24/2012 08:59 PM, James Brown wrote:
I cannot find signatures on the web-pages of scratchbox-project which
used for signing the packages from ist repos.
Are their exist?
There are none.
The repository is not signed.
Regards,
Jussi
___
Scrat
New releases:
=
* scratchbox-core 1.0.27
* scratchbox-libs 1.0.27
* scratchbox-toolchain-host-gcc 1.0.27
Highlights:
===
* Support for /run on systems that have it
* Debian: more careful with bindmounts when uninstalling (#330)
* Faster upgrades from previous versions if sev
On 01/18/2012 04:58 PM, Adam Magaluk wrote:
What is the best way to share a folder available on the host system to
the scratchbox environment when I run /scratchbox/login
If you want just to temporarily move files, /tmp is the same in and
outside scratchbox.
Currently I keep having to copy
On 12/16/2011 01:44 PM, Guillermo Rodriguez wrote:
After a lot of testing I found that I needed to "reset" the target (sb-conf
reset)
in order to fix this. I don't have a clue why this is needed and why the -march
setting
was being ignored without this, but at least it is now solved.
What did
On 12/14/2011 02:40 PM, Guillermo Rodriguez Garcia wrote:
I am trying to use scratchbox to compile code for an armv4t target.
However the available ARM toolchains seem to be ignoring the -march
option, hence generating code that will not run on the target device.
I have installed the latest hath
On 12/07/2011 05:06 PM, Adam Magaluk wrote:
I figured it was something to do with that, Im just not
very knowledgeable on how exactly binfmt_misc works.
Any ideas on how I could get both of my development strategies working?
Well, the easiest way is to set qemu-arm from your host once again to
On 12/07/2011 01:54 AM, Adam Magaluk wrote:
Finally I normally run to chroot into my newly created arm emdebian system.
sudo chroot EmDebian /
But as soon as I install scratchbox-core I get the following error
on sudo chroot EmDebian
chroot: failed to run command `/bin/bash': No such f
On 10/18/2011 02:05 AM, Antoine Bouthors wrote:
I'm trying to setup scratchbox to cross-compile for an ARM target. I got
scratchbox setup and got past the helloworld examples and qemu, and now
I would like to try sbrsh.
I have installed sbrshd on the device and sbrsh on the host, and it all
seem
On 10/11/2011 02:32 AM, Kristen Eisenberg wrote:
New releases:
=
* scratchbox-core 1.0.23
* scratchbox-libs 1.0.23
* scratchbox-toolchain-host-gcc 1.0.23
* scratchbox-devkit-debian-squeeze 1.0.7
Please refrain from reposting old release notes in the mailing list.
Regards,
Jussi
On 09/07/2011 12:55 PM, Athanasios Silis wrote:
I shall continue with some questions if I may :) ... please!
is info about the instruction set stored in an executable? ie can i
verify the version of the arch of an executable, just as I can find out
the arch using the command 'file' ?
You might
On 09/06/2011 05:22 PM, Athanasios Silis wrote:
I have managed to setup a target with:
Issuing sb-conf show without arguments will give you complete output :)
the arch as i see from gcc -v is --with-arch=armv5te
which is not suitable for me, i am attempting to get the older
codesourcery toolc
On 09/06/2011 02:01 PM, Athanasios Silis wrote:
Then I guess its the
scratchbox-toolchain-arm-linux-cs2010q1-202-1.0.17-2-i386.tar.gz the
toolchain I will need..? where can I read info about the specific toolchain?
The compiler will tell how it was configured if you issue a command like
gcc -v
On 09/05/2011 07:23 PM, Athanasios Silis wrote:
considering this processor:
-should i go for the latest scratchbox packages? (1.0.26)
-should I go for Hathor or Apophis, there doesn't seem to be any
pros/cons information out there.
Go for the latest scratchbox packages.
The architecture you're
On 09/01/2011 07:11 PM, tgrs tfyguhi wrote:
After a little more investigation, it appears that it appends only with
the target arm-linux-cs2010q1-202. I deleted and recreated the target,
just to be sure, but that was not the problem.
Can you give me the output of sb-conf show on that target?
On 08/31/2011 07:03 PM, tgrs tfyguhi wrote:
But the binary is NOT the same if I use 'gcc' provided by the target, or
if I directly use
/scratchbox/compilers/arm-linux-cs2010q1-202/bin/arm-none-linux-gnueabi-gcc.
(If I understand properly how Scratchbox works, it's supposed to be the
same gcc)
W
On 07/03/2011 01:25 AM, Ron Hermsen wrote:
python-host ~/sb-toolchain-extras/confhelper/create_toolchain_conf.py
is working.
... and that's the preferred way of using it.
Changing the interpreter explicitly to python-host would make the script
executable only from within scratchbox.
Bu
On 07/03/2011 01:25 AM, Ron Hermsen wrote:
I tried to install the same setup as I did a year ago (SB1.0.17), and
each time I try to setup the new target I get: Failed to install
C-libraty to tarket: DV20x0
I even re-installed everything from scratch twice, but same results.
(Using the current 1.
On 06/22/2011 08:05 PM, Ron Hermsen wrote:
The wiki is asking for “scratchbox-devkit-cputransp”, but this is
missing in the Hathor download directory [2].
What is the solution for this?
The wiki is quite outdated.
You want to install scratchbox-devkit-qemu instead, unless you
explicitly want
New releases:
=
* scratchbox-core 1.0.26
* scratchbox-libs 1.0.26
* scratchbox-toolchain-* 1.0.26
Highlights:
===
* Fix an issue with unnecessary warning when umounting bindmounts
on recent linux distributions
Notes:
==
* Hathor r1 wiki page [1] contains the informat
New releases:
=
* scratchbox-core 1.0.25
* scratchbox-libs 1.0.25
* scratchbox-toolchain-host-gcc 1.0.25
* scratchbox-devkit-qemu 0.13.90-0rabbit1
* scratchbox-toolchain-* 1.0.24
Highlights:
===
* Qemu 0.13
* Various minor fixes both on scratchbox and the toolchain packaging
On 05/12/2011 07:06 PM, Diane Holt wrote:
Just FYI, I found the error. The make process requires the C++ headers
be at /scratchbox/compilers//compiler-name//include/c++ -- mine were at
/scratchbox/compilers//compiler-name//arm-linux-gnueabi/include/c++.
It didn't complain about missing headers
On 05/12/2011 05:00 AM, Diane Holt wrote:
Did you post your linaro on the downloads page? (All I see are ones
named cs*, which I assume are CodeSourcery ones.)
Did not, I've recompiled the toolchain and added 2 patches so it's not
exactly official linaro one :)
However, if you want to try it
On 05/05/2011 10:42 AM, Diane Holt wrote:
This time, I didn't get any of that. There's
no error in the make output, there's just no mention of those things at
all. I also just noticed that, while I do have a device_tools subdir,
there's no Makefile in it. There's one in meta/device_tools, but not
On 03/12/2011 01:00 AM, Diane Holt wrote:
Is there any chance that the host_shared libc will ever be updated?
As far as I know, there's no plans at least from the usual parties
that've been sponsoring scratchbox development.
If not officially, is there a way a person could do it for themsel
New releases:
=
* scratchbox-core 1.0.24
* scratchbox-libs 1.0.24
* scratchbox-toolchain-host-gcc 1.0.24
* scratchbox-devkit-python-legacy 1.0.2
Highlights:
===
* /usr/bin/python is no longer provided by scratchbox, you can
find the built-in python as python-host. Select p
New releases:
=
* scratchbox-core 1.0.23
* scratchbox-libs 1.0.23
* scratchbox-toolchain-host-gcc 1.0.23
* scratchbox-devkit-debian-squeeze 1.0.7
Highlights:
===
* Fixes sync script breakage on x86_64 when scratchbox installed
in a custom path
* Fixes issue with sb-conf/sb
On 12/17/2010 09:55 AM, Vaclav Barta wrote:
So, what is the best (simplest to install, most stable)
scratchbox toolchain for a big-endian platform?
If you find a toolchain, you can import it into scratchbox using
instructions from [1].
Regards,
Jussi
[1] http://scratchbox.org/wiki/Foreig
New releases:
=
* scratchbox-core 1.0.22
* scratchbox-libs 1.0.22
* scratchbox-toolchain-host-gcc 1.0.22
* scratchbox-devkit-autotools-legacy
* scratchbox-devkit-debian 1.0.12
* scratchbox-devkit-debian-squeeze 1.0.6
* scratchbox-devkit-doctools 1.0.15
Highlights:
===
* Auto
testing 123
___
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
On 09/02/2010 09:45 AM, chao yu wrote:
My target CPU is s3c2440 which is arm v4t architecture and I want
to compile a executeable binary to run on it. I added the parameter
-march=armv4t and built. But I found before link, the object file is
armv4t. After link stage, the generated file is ar
On 08/25/2010 03:46 PM, Antoni Silvestre Padrós wrote:
Hi, I've compiled a foreign toochain and was about to setup my target
with sbrsh but when I get to the transparency method screen of the
sb-menu command there is no sbrsh option.
Do you have cputransp devkit installed and selected for your
New releases:
=
* scratchbox-core 1.0.19
* scratchbox-libs 1.0.19
* scratchbox-toolchain-host-gcc 1.0.19
* scratchbox-devkit-git 1.0.2
* scratchbox-devkit-mtd 1.0.3
Highlights:
===
* Files are copied cleanly to targets and everything on target
is unconditionally overwritte
On 06/09/2010 01:33 PM, Raghavendra. S wrote:
I saw that in some forum's they mentioned about
/scratchbox/device_tools.
In the stable branch the device tools come from toolchain extras.
The part you're referring to might be the device_tools from the old
toolchains repo, from the time befo
On 06/09/2010 12:06 PM, Raghavendra. S wrote:
Hi All,
I am getting error while adding foreign tool chain.
# cd /scratchbox/sb-toolchain-extras/
# make CONFIG=meta/alien-tc/arm-none-linux-gnueabi.conf -C
Why is your sb-toolchain-extras repository located in the top level of
scratchbox direct
On 06/09/2010 12:05 PM, Raghavendra. S wrote:
Please let me know what all things I should edit for my compiler. I am
getting above error. Please let me know why this error is accuring.
There's already a scratchboxified version available from that compiler
in the Hathor repository [1].
Check
On 06/12/2010 12:02 AM, Diane Holt wrote:
What about vm.mmap_min_addr -- does that still need tweaking, or is that
corrected as well?
That was strictly a qemu related issue which hasn't been present for a
while in the new qemu devkits.
However, there was a kernel version which had a clever s
Scratchbox Hathor is now the latest release of the stable branch. Hathor
will be the successor of Apophis.
Since the releases are of the same stable branch most packages are
usable as-is on the new scratchbox, although it's recommended to use
packages only from the Hathor release if they're av
Mika Westerberg wrote:
That wiki page is for sb1 and seems to be outdated as mmap_min_addr setting is
not needed anymore (QEMU handles this automatically).
Yes, new qemu versions handle that automatically.
However, for sb1 you need to use qemu devkit, cputransp devkit contains
older version w
New releases:
=
* scratchbox-devkit-debian-squeeze 1.0.3
Highlights:
===
* Fixed the issue with missing perl library on certain perl
based scripts
* Fixed the issue of install-info busylooping, when a certain version
of install-info installed on target
Notes:
==
*
Aaron Brice wrote:
I'm on a RHEL 5 host system, using scratchbox2 and the latest 4.4
CodeSourcery IA32 toolchain. It seems like it's linking against the
host system ancient glibc (libc-2.5.so) instead of the toolchain's
glibc (libc-2.10.1.so):
You are building the kernel inside scratchbox? May
Jeff Hoogland wrote:
Per the advice I found here -
http://www.mail-archive.com/maemo-develop...@maemo.org/msg14442.html -
I did the following:
SBOX_REDIRECT_IGNORE=/usr/bin/perl
Which appears to have half worked - my perl versions now shows 5.8.3
(instead of 5.8.4) however when I try to compile
Hello all,
Seems the change to new server left us without mailinglists for quite a
while. The issue has now been fixed and everything should be back to normal.
Sorry about the inconvenience.
Regards,
Jussi
___
Scratchbox-users mailing list
Scratc
New releases:
=
* scratchbox-toolchain-cs2007q3-glibc2.5-arm7
* scratchbox-toolchain-cs2007q3-glibc2.5-i486
Highlights:
===
* Recompiled the toolchains to include fix for dwarf2out-pr31899
http://gcc.gnu.org/bugzilla/attachment.cgi?id=14286
* Added a separate changelog fil
New releases:
=
* scratchbox-devkit-debian-squeeze 1.0
Highlights:
===
* New, minimal devkit containing squeeze versions of debian tools
Software changes:
=
* debian-squeeze
* New
* apt
* debhelper
* debianutils
* dpkg
Notes:
==
* Ne
Enrique Poves wrote:
Solved. It was just a problem with my Antivirus sw.
# file Packages.gz
Packages.gz: ASCII English text
Anybody can give a clue about what's going on?
Apparently your antivirus extracted the archive to see if it contained
anything malicious :P
The original file is as i
Kartik Natarajan wrote:
No package 'glib-2.0' found
I have tried everything I could possibly do, I have libglib2.0-dev
installed on my system. Please help.
System meaning your host system?
You need to have it compiled and installed to your target. When you
login to scratchbox, you're essent
Scratchbox's host compiler is old. As is the glibc...
Part of the reason is the somewhat improper way it's built, the whole
core set of tools should be upgraded to a modern era but that's quite a
bit of work.
Regards,
Jussi
Rasjid Wilcox wrote:
New to scratchbox. I'm compiling a number o
Pradeep Patil wrote:
Don't know where this is the right place to post or not. I have just
installed scratchbox on my Linux machine and i am following this
tutorial:
It is the correct place.
when i run this i get following error: $
/scratchbox/compilers/bin/arm-linux-gcc -Wall -o arm-hello hel
For basic scratchbox setup, grab core, libs and a set of
devkits/toolchains of your choice.
The issue you're having is due to old host-side glibc inside scratchbox
that can be circumvented with [1]. See also [2] for further known issues.
Regards,
Jussi
[1]
echo 0 | sudo tee /proc/sys/kern
New releases:
=
* scratchbox-core 1.0.16
* scratchbox-libs 1.0.16
* scratchbox-toolchain-host-gcc 1.0.16
Highlights:
===
* Fixes issues with custom system directories when
selecting a target
Notes:
==
* Apophis R4 wiki page [1] contains the information on known issue
New releases:
=
* scratchbox-toolchain-cs2007q3-glibc2.5-arm6
* scratchbox-toolchain-cs2007q3-glibc2.5-arm7
* scratchbox-toolchain-cs2007q3-glibc2.5-i486
Highlights:
===
* Recompiled the toolchains to include eventfd support
(taken from eglibc 2.9)
* Add -mfpu=neon specifi
New releases:
=
* scratchbox-core 1.0.15
* scratchbox-libs 1.0.15
* scratchbox-toolchain-host-gcc 1.0.15
Highlights:
===
* Fixed the issues with copying /etc/hosts
* Upgraded gettext to 0.17
Notes:
==
* Apophis R4 wiki page [1] contains the information on known issues
New releases:
=
* scratchbox-devkit-apt-https 1.0.9
Highlights:
===
* Fixed the issues with extra long dependecy fields
Notes:
==
* Apophis R4 wiki page [1] contains the information on known issues
and other release specific things.
Report bugs to scratchbox.org bug
New releases:
=
* scratchbox-devkit-doctools 1.0.13
Highlights:
===
* Added a workaround for the 5 year old issue in tetex [1]
Notes:
==
* Apophis R4 wiki page [1] contains the information on known issues
and other release specific things.
* From previous release ann
New releases:
=
* scratchbox-devkit-doctools 1.0.12
* scratchbox-toolchain-cs2007q3-glibc2.5-arm6
* scratchbox-toolchain-cs2007q3-glibc2.5-arm7
* scratchbox-toolchain-cs2007q3-glibc2.5-i486
Highlights:
===
* Recompiled the toolchains to include another profiling fix for arm [
The options are specified in the source package [1], particularly in
debian/rules.
Regards,
Jussi
[1]
http://scratchbox.org/download/files/sbox-releases/apophis/src/qemu_0.10.0-0sb5.tar.gz
LETALLEC Jean-Francois wrote:
First of all, Hello :-) I'm new in the world of cross-compilation and
New releases:
=
* scratchbox-devkit-apt-https 1.0.7
Highlights:
===
* Apt no longer defaults to install recommended packages
* Fixed an issue with leftover development files sometimes
contaminating the build process inside scratchbox
* Reverted upstream patch which caused a
New releases:
=
* scratchbox-devkit-apt-https 1.0.6
Highlights:
===
* Apt no longer returns an error when target has no
log directory (log is not written by default)
Notes:
==
* Apophis R4 wiki page [1] contains the information on known issues
and other release spec
New releases:
=
* scratchbox-toolchain-cs2007q3-glibc2.5-arm6 1.0.11-7
* scratchbox-toolchain-cs2007q3-glibc2.5-arm7 1.0.11-8
* scratchbox-toolchain-cs2007q3-glibc2.5-i486 1.0.11-6
Highlights:
===
* Recompiled the toolchains to include profiling fix for arm [1]
(requires ne
New releases:
=
* scratchbox-core 1.0.14
* scratchbox-libs 1.0.14
* scratchbox-toolchain-host 1.0.14
* scratchbox-devkit-apt-https 1.0.5
* scratchbox-devkit-doctools 1.0.11
* scratchbox-devkit-qemu 0.10.0-0sb5
Highlights:
===
* New, independent qemu devkit containing up-to-d
New releases:
=
* scratchbox-toolchain-cs2007q3-glibc2.5-arm7 1.0.10-6
* scratchbox-toolchain-cs2007q3-glibc2.5-i486 1.0.10-4
* scratchbox-toolchain-arm-linux-cs2007q1-21sb1 1.0.10-1
* scratchbox-toolchain-arm-linux-cs2007q3-51sb3 1.0.10-1
* scratchbox-toolchain-arm-linux-cs2008q3-72
New releases:
=
* scratchbox-core 1.0.13
* scratchbox-libs 1.0.13
* scratchbox-toolchain-host 1.0.13
* scratchbox-devkit-apt-https 1.0.4
* scratchbox-devkit-cputransp 1.0.9
Highlights:
===
* Support for sysv fakeroot on non-sbrsh targets
* Additional syscalls supported for q
Eade, Sean (SCR US) wrote:
I am trying to do an update of the debian packages installed in my
Scratchbox environment but when I do 'apt-get update' I get the
following error. I can't seem to get access to the servers through the
scratchbox - but I have the http_proxy env variable set correctly an
Eade, Sean (SCR US) wrote:
I have been trying to follow this tutorial, to use the scratchbox:
http://www.scratchbox.org/documentation/user/scratchbox-1.0/html/installdoc.html
That tutorial maybe sadly a bit out of date.
But I can’t find the toolchain
*scratchbox-toolchain-arm-gcc3.3-glibc2.3
New releases:
=
* scratchbox-devkit-doctools 1.0.10
* scratchbox-toolchain-arm-linux-cs2007q1-21sb1 1.0.9
* scratchbox-toolchain-arm-linux-cs2007q3-51sb3 1.0.9
Highlights:
===
* 2 CS toolchains previously packages only unofficially have now
been repackaged and made officia
Probably you have no locate db in your target.
Additionally I'm unsure anyone's actually using Scratchbox's locate and
how well it works in general.
You can probably find the directory in /usr/lib/pkgconfig and/or
/usr/share/pkgconfig.
Regards,
Jussi
surabhi dwivedi wrote:
Hello Locate
Why are you trying to run the gcc wrapper directly? And why are you
trying to execute gcc 4.3 when your toolchain's gcc is 4.1?
Try the following:
% gcc -Wall -g /scratchbox/packages/hello.c -o hello-arm
Also, it would be helpful to know the configuration of the target you're
attempting to do
I'd suggest using the latest release unless you have a reason to use
that particular version.
However, older releases can be found in [1].
Regards,
Jussi
[1] http://scratchbox.org/download/files/sbox-releases/branches/
Ville Hyttinen wrote:
I'm following the instructions on web page
http:
New releases:
=
* scratchbox 1.0.12
* scratchbox-devkit-cputransp 1.0.8
Highlights:
===
* Fixes issues with seemingly random segmentation faults with user space
qemu (needs both scratchbox 1.0.12 and cputransp devkit 1.0.8)
* Add support for just installing libgcc_s from s
Also in the scratchbox.org wiki, Apophis R4 page, listed under known
issues :)
http://scratchbox.org/wiki/Apophis-r4
Regards,
Jussi
Kalle Vahlman wrote:
2008/12/23 vandy linux :
I am using cpu transparency as u told , getting errors then also, I am
attaching the config.log here .
confi
Velikanov, Mikhail wrote:
However, I'm beginning to think that the most sensible plan would be
just to upgrade the host-side glibc to a less ancient level.
This won't really prevent this problem from happening, although it'll
probably make it more rare. There is always a chance someone might
co
Velikanov, Mikhail wrote:
Unfortunately, just copying the binary and the libs it requires under
/host_usr didn't work. When I tried to run it inside Scratchbox, the
default dynamic loader in /scratchbox/host_shared/lib was used to load
the libs, and that produced a bunch of libc version incompati
Or you can try to copy the binary (and additional libraries it needs)
under /host_usr/, in most of the cases, that works too.
Or, you can use a statically linked binary...
Regards,
Jussi
Diane Holt wrote:
You can run statically linked executables inside Scratchbox that were
built outside o
The scratchbox.org bugzilla is now finally back online.
Sorry about the delay, it's been a huge mess with hosting issues,
hopefully everything is now sorted and we can get back to business as
normal.
In the progress the debian system running in the server was upgraded
closer to present date,
holger krekel wrote:
i am currently experimenting with cross-compilation of large
C-files. For this, i need to use the cross-compiler from the
hosting end because compiling in the virtual environment takes
around 10 times as long (but succeeds). If i follow the 1.0
tutorial and use the cs2005q3
New releases:
=
* scratchbox-toolchain-cs2007q3-glibc2.5-arm6 1.0.8-5
* scratchbox-toolchain-cs2007q3-glibc2.5-arm7 1.0.8-6
* scratchbox-toolchain-cs2007q3-glibc2.5-i486 1.0.8-3
Highlights:
===
* Recompiled the toolchain with the following patches:
* fix for the issue with
New releases:
=
* scratchbox-core 1.0.11
* scratchbox-libs 1.0.11
* scratchbox-toolchain-host-gcc 1.0.11
* scratchbox-devkit-git 1.0.1 [1]
* scratchbox-devkit-svn 1.0 [1]
Highlights:
===
* In the interest that debug symbols are actually found,
added new option to install
Daniel Bainton wrote:
If that's the case, we have to fix it...
Just do a "echo $PATH" in SB. I doubt /host_usr is before the devkits
and core for you either. Isn't there a bug for this? Atleast it's been
mentioned in IRC... :)
Fixed in the vcs head.
Yeah, the bugzilla is still offline...
Re
Daniel Bainton wrote:
That, or you can do as Kalle suggested and compile a newer version of python
for the host architecture and put it inside /host_usr/. After that you won't
need any environment variables since stuff in /host_usr/ always override the
stuff in devkits and the core.
That is, it
Thomas Petazzoni wrote:
I tried to integrate an ARM and MIPS toolchain, generated by Buildroot,
into Scratchbox using sb-toolchain-extras. These toolchains have been
successfully integrated, and they are able to generate binaries that
can be transparently executed by Scratchbox.
However, at the
Mateusz Jan Dominikowski wrote:
SB comes with Python version 2.3.4 so I compiled 2.5.2 from sources and
installed it with standard prefix (/usr/local).
As /usr/local/bin is redirected in SB I tried to export
SBOX_REDIRECT_IGNORE=/usr/local/bin/python.
However when I type 'python' I still get ve
Thomas Petazzoni wrote:
As far as I've understood, and my experiments tend to confirm this, the
toolchain must have been generated in a /scratchbox/compilers/
directory in order to be integrated into Scratchbox. Moreover, the
toolchain must be compiled against the Scratchbox environment, notably
New releases:
=
* scratchbox-devkit-doctools 1.0.9
Highlights:
===
* Fixed DocBook issue with missing catalogs DocBook
* Fixes issue with building JadeTeX
Notes:
==
* Apophis R4 wiki page [1] contains the information on known issues
and other release specific things
And, if you want, you can do additional bindmounts outside scratchbox as
well (you have to be root to do those). Do note that stopping scratchbox
with sbox_ctl will remove the scratchbox provided bindmounts but will
not touch any additional mount you have created. Make sure you umount
all custo
Indeed. It would seem that the problem of selecting compat vdso support
from the proc filesystem affects mostly 64 bit stock kernels.
Regards,
Jussi
Graham Cobb wrote:
By the way, if you are running a 64-bit kernel then
the /proc/sys/vm/vdso_enabled file will not exist and the only option i
Ian Burrell wrote:
No. Fedora 9 is using 2.6.25 (latest is 2.6.25.10-86.fc9). As I
said, the kernel is compiled without CONFIG_COMPAT_VDSO. It looks
like this causes the /proc/sys/vm/vdso_enabled file to not exist. My
impression is that the kernel config is a result of using
CONFIG_VIRTUALIZAT
Unfortunately, this has been the case for some time.
Apparently there has been miscommunication about upgrading the database
behind this relatively ancient version of bugzilla and the upgraded
database (which contains stuff for other applications as well) is
incompatible with the bugzilla...
Ray Kiddy wrote:
I started with the
present http://www.scratchbox.org/documentation/user/scratchbox-1.0/html/installdoc.html
and added info to the wiki pages
at http://www.scratchbox.org/wiki/ScratchboxInstallation
and http://www.scratchbox.org/wiki/ScratchboxTargetConfiguration. A lot
of tha
Janne Kataja wrote:
Ian Burrell wrote:
No. Fedora 9 is using 2.6.25 (latest is 2.6.25.10-86.fc9). As I
said, the kernel is compiled without CONFIG_COMPAT_VDSO. It looks
like this causes the /proc/sys/vm/vdso_enabled file to not exist. My
impression is that the kernel config is a result of usi
This is a qemu problem.
The version of qemu you're using cannot run the binaries produced by
your toolchain. This makes your configure to fail too as it just tries
to run the compiled test program and will stop whenever the compiled
binary exits with a code other than 0.
Regards,
Jussi
s
Ian Burrell wrote:
I am unable to get scratchbox (for Maemo 4.1 SDK) working on Fedora 9.
I saw lots of places talking about disabling VDSO. The problem is
that Fedora 9 does not have /proc/sys/vm/vdso_enabled file. It looks
like the kernel is configured without compat VDSO support.
Indeed.
Wednesday 25 June 2008 08:26:24 am Jussi Hakala wrote:
E Robertson wrote:
I get this when I run that comand:
sb-conf: No fakeroot versions found for compiler: host-gcc
Ah, yes.
I don't know what I was thinking when I wrote that, sorry :)
Is the error message the same if you try to run a
E Robertson wrote:
I get this when I run that comand:
sb-conf: No fakeroot versions found for compiler: host-gcc
Ah, yes.
I don't know what I was thinking when I wrote that, sorry :)
Is the error message the same if you try to run anything else under
fakeroot, for example:
$ fakeroot ls -
Interesting error.
Try [1], and see if that solves your problem.
Regards,
Jussi
[1] sb-conf in HOST -F
E Robertson wrote:
Hi All,
I'm attempting to use a foreign toolchain and I seem to be stuck at
building the auxiliary tools. I followed all the instructions so far,
and unless I'm missing
The most reliable thing would be probably to test the presence of a
scratchbox-like directory layout [1] or if env output contains any SBOX_
prefixed variables [2] (but this may lead to ambiguity between sb1 and sb2).
Regards,
Jussi
[1]
if [ -e /targets/links/scratchbox.config ] ; then
..
New release:
* scratchbox-devkit-maemo3 1.0.3
Highlights:
* Etch version of openssl, complete with fixes for
the randomness issue
* Fixed an issue with quilt and missing files
Report bugs to scratchbox.org bugzilla.
Happy hacking,
Jussi
___
Scr
1 - 100 of 197 matches
Mail list logo
