Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2004-01

Having FPC linker errors saved to a file

3 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Eric Grange

Is there a way to have the linker errors saved to a file (under Win32, 1.9.1) instead of just listed in the DOS box?

The -Fe catches compilation errors and messages, but linker issues (such "undefined reference to SomeSymbol") are listed only in the DOS Box. I've tried to redirect output to a file via a "> errorfile.log" appended at the end of the command line, but that doesn't have any effect... only the "Error while linking" message goes to the file.
Any ideas or is it a limitation of ld.exe?

Eric

Reply by email

Marco van de Voort
to Eric Grange
Show quoted text 9 lines
Is there a way to have the linker errors saved to a file (under Win32, 1.9.1) instead of just listed in the DOS box? The -Fe catches compilation errors and messages, but linker issues (such "undefined reference to SomeSymbol") are listed only in the DOS Box. I've tried to redirect output to a file via a "> errorfile.log" appended at the end of the command line, but that doesn't have any effect... only the "Error while linking" message goes to the file. Any ideas or is it a limitation of ld.exe?

It goes to stderr, and you also have to pipe stderr.

Under dos I believe &> is used to pipe both stderr and stdout to file, under unix it is >&.

Reply by email

Eric Grange
to Marco van de Voort
Under dos I believe &> is used to pipe both stderr and stdout to file, under unix it is >&.

Thanks :)
Starting on that I found the DOS syntax: "2>".

I'll probably use another approach than redirection to file in the end, to allow some more "interactive" compilation progress report.

Eric

Reply by email