Re: [fpc-pascal] Building FPC with gdb support for SPARC
> On 14 Aug 2006, at 23:58, Mark Morgan Lloyd wrote:
>
> >> OK, noted for reference. I was assuming that the addition was to
> >> the FPC stuff
> >> rather than the toolchain.
> >
> > Requires gcc.o, which I presume implies that the entire toolchain
> > has to be on
> > the system. Can I generate that without risking breaking things?
>
> No, it should require libgcc.a, which should be installed on your
> system already.
In a later msg you say {$l gcc} instead of {$linklib gcc}.
It should be the latter.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Building FPC with gdb support for SPARC
On 15 Aug 2006, at 09:35, Marco van de Voort wrote:
No, it should require libgcc.a, which should be installed on your
system already.
In a later msg you say {$l gcc} instead of {$linklib gcc}.
Ah yes, of course.
Jonas
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Building FPC with gdb support for SPARC
Jonas Maebe wrote:
> > In a later msg you say {$l gcc} instead of {$linklib gcc}.
>
> Ah yes, of course.
Yes, I was looking at that commented-out line. I've set another build going,
I'll be back in about six hours...
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Compiling for SPARC
On 14 aug 2006, at 15:33, Jonas Maebe wrote:
> I forgot to add some more relevant code:
>
> Replace(cmdstr,'$LIB',maybequoted(current_module.staticlibfilename^));
> { create AR commands }
> success := true;
> nextcmd := cmdstr;
> current := TStringListItem(SmartLinkOFiles.First);
> repeat
> Replace(nextcmd,'$FILES',GetNextFiles(240 - length(nextcmd) +
> 6 - length(binstr) - 1, current));
> success:=DoExec(binstr,nextcmd,false,true);
> nextcmd := cmdstr;
> until (not assigned(current)) or (not success);
>
> The first replace already puts the library name in the string. So if
> the directory + name of that library (which always is in a subdir of
> the unit output directory) is around 120 chars, things do add up.
>
> Not sure how to fix this properly though, except by finally doing
> that whole "replace Dos and shortstrings with Sysutils and
> ansistrings for all external interfacing in the compiler" thing.
I think that for the moment I'd settle for an explicit warning and/or error
message, the first triggered when a path+file gets to be longer than around 105
characters and the second fatal.
I'm hoping that at some point I'll be familiar enough with things that I might
be some use working through problems like this, but I've got a long way to go
yet and a lot of problems on my plate at this end.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Compiling for SPARC
On 15 Aug 2006, at 12:06, Mark Morgan Lloyd wrote: I'm hoping that at some point I'll be familiar enough with things that I might be some use working through problems like this, but I've got a long way to go yet and a lot of problems on my plate at this end. FWIW, I wouldn't spend too much time on trying to get the text mode IDE (fp) compiled with GDB support at this moment, unless you really want to use it later on. It's something which is quite separate from most problems you'll encounter when compiling your own programs. Jonas ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Building FPC with gdb support for SPARC
The build worked and I appear to have an intact fpc and fp. However fp's disassembly window is very fragile- SEGV at the drop of a hat. I find I can't transfer the compiled bundle to another machine- I get "fp: /lib/libc.so.6: version `GLIBC_2.3' not found (required by fp)" which I presume is telling me that it can't find the library version it was built against. I'm going to drop that as an experiment since that machine is too ponderous to build the compiler in less than a day, and upgrading anything on it isn't feasible. Going back to the SEGV problem, is there any way that somebody with my minimal experience can tackle this? -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
