[Openmcl-devel] resolved problem with ccl on Linux ARM
gb at clozure.com
Wed Feb 24 08:11:03 PST 2016
I don't think that CCL cares where the text segment starts on ARM Linux
any more, though it once did
(for fairly bloodcurdling reasons.)
If you get a chance, could you try:
1 running ccl on your tegra, noting the pid of the resulting process
2 in another shell, doing
$ cat /proc/PID/maps/
/and letting me see the output ?
whatever may be there, there is no reason for the linker script to
clobber it, but I'm
As far as I know, we should change or remove the custom linker script.
On 02/24/2016 01:58 AM, Timothy Moore wrote:
> I was unable to run ccl on an NVidia Tegra running Arch Linux. The program would be killed immediately on startup; I couldn't even start it using gdb. The problem turned out to be that the start of the executable's text segment was mapped to address 0x0 (or at least to a low address), which is reserved in this configuration. I changed the linker script to initialize the beginning of the text segment in the same way that the default script does; I'm happy to report that ccl works very well on this Acer Chromebook now.
> I have no idea if the memory map is particular to Arch Linux, or this version of the kernel (3.10.18 arm7l), the ARM version, or what. Here is the /proc/cpuinfo for one (out of four) processor:
> processor : 0
> model name : ARMv7 Processor rev 3 (v7l)
> BogoMIPS : 22.84
> Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae
> CPU implementer : 0x41
> CPU architecture: 7
> CPU variant : 0x3
> CPU part : 0xc0f
> CPU revision : 3
> Attached is my fix to the linker script. I don't know if this is sufficiently generic to work for Linux on ARM in general.
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel