> 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 gener
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 -
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
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(SmartLinkOF
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 muc
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 tell
