[Simh] Cross-assemblers, cross-compilers: success! (so far)

[Jordi Guillaumes i Pons]

Al 25/07/12 12:05, En/na Jan-Benedict Glaw ha escrit:
> On Wed, 2012-07-25 11:10:58 +0200, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
>> Al 25/07/12 11:07, En/na Jan-Benedict Glaw ha escrit:
>>> On Wed, 2012-07-25 10:37:23 +0200, Jan-Benedict Glaw <jbglaw at lug-owl.de> wrote:
>>>> On Wed, 2012-07-25 10:25:13 +0200, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
>>>>> Al 25/07/12 10:16, En/na Jan-Benedict Glaw ha escrit:
>>>>>> On Wed, 2012-07-25 00:05:27 +0200, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
>>>> [...]
>>>>> jguillaumes at eeepc2jordi:~$ pdp11-aout-ld
>>>>> pdp11-aout-ld:built in linker script:7: syntax error
>>>> And GCC? I cannot yet tell about it, it's still building. Takes some
>>>> more time than binutils...
>>> GCC is readily built (from GIT repository)!
>> Nice! Did you build the master branch or did you select any tag?
> jbglaw at darkeye:/mnt/devel/src/linux$ cat gcc/.git/config |grep url
>          url = git://gcc.gnu.org/git/gcc.git
> jbglaw at darkeye:/mnt/devel/src/linux$ (cd gcc && git branch)
> * master
I've got a basic idea about which is the problem with ld. It's related 
to LIBPATH. For some reason it puts the contents of LIBPATH in the 
generated script:

/* Default linker script, for normal executables */
OUTPUT_FORMAT("a.out-pdp11", "a.out-pdp11",
               "a.out-pdp11")
OUTPUT_ARCH(pdp11)
SEARCH_DIR("/usr/local/pdp11-aout/lib");
/opt/orahome/tuxedo10gR3/lib:/usr/lib/jvm/java-6-sun/lib/i386/server:/usr/lib/jvm/java-6-sun/jre/bin:/opt/cobol-it/lib:
PROVIDE (__stack = 0);
SECTIONS

I understand it should not even try to use the native LIBPATH in a 
cross-build environment. Actually, it looks like some bug in the 
genscripts.sh script, since it just spews $LIBPATH without proper 
"bracketing" (ie, using SEARCH_DIR($LIBPATH)).

I've manually edited the generated scripts and the epdp11.c source file 
and I've rebuilt binutils. Now it works OK. I'll try to file a bug 
report about this.