Mail Archives: djgpp/1997/03/10/19:47:46
Hallo Leute,
gfoot AT mc31 DOT merton DOT ox DOT ac DOT uk (George Foot) meinte am 07.03.97
zum Thema "Re: make conflicts with turbopascal":
>: k:\binpatch>g:\dos_gcc\BIN\make -f testy2
>: f:\bp\bin\bpc
>: make.exe: *** [all] Error -1
>
>What happens if you type `f:\bp\bin\bpc'? Does it work? What make is
>saying here is that bpc returned exit code -1. Normally non-zero exit
>codes indicate errors, so make quits at that stage.
Yes. It works fine. If I try *another* make (the one that came with
Delphi), *there* it works fine, but it doesn't work with the one that
comes with djgpp. The same makefile, the same DOS command line, but one
make wouldn't launch bpc without failure where the other one does.
>I haven't used bpc, but I would have expected it to take some command
>line parameters, to tell it what to compile. Is this not the case?
>Your makefile doesn't contain any.
I've made a makefile as simple as possible. Without commands bpc should
print its' usage information and then quit (successfull).
I've tried DCC32.EXE (the command line version of the delphi 2 compiler)
which works fine with djgpp's make. But programs compiled as command
line applications also conflict with djgpp's make. But I need to compile
some pascal utilities somewhere. At the moment, I'm converting to p2c
and gcc as these are needed for linux anyway.
To me it seems that there is something with the DPMI that causes these
problems.
Obviously GNU-make has a lot more features over all over make's. I'd
like to have one that does not restrict me on what programs it can run,
any ideas on this?
Mls, Kay
-- =
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
>>Shareware nutzen ist gut, sie zu registrieren auch.
>Diese Nachricht besteht zu 100% aus recycelten Elektronen.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
- Raw text -