On Fri, Mar 10, 2000 at 02:11:03PM -0300, Alexandre Oliva wrote:
>
> Then please explain how come pexecute prints that message.
>
> I assume you're running on some Unix flavor, probably GNU/Linux, so
> the last variant of pexecute is used. The only situation in which
Yes.
> program (gcc); program is the name of the program to be exec()ed
> (collect2). I can't think of any way collect2 might arrange for the
> process that exec()ed it to print that error message. How did you
> make sure that collect2 was properly exec()ed?
>
I even ran ld-new by hand. That is how I tracked down the problem.
With my patch based on Ian's suggestion, everything works fine now.
H.J.
