Hi,
I have this problem when running 2.5.22, make can't run itself inside a
Makefile.
Let's say I have this Makefile:
test:
( make -v )
It fails saying this:
( make -v )
make: *** [test] Error 139
I don't have any idea about what can be causing this error, might be something
to do with reiserfs...
Any ideas?
--
Felipe Contreras
139 return code means that the process that make was running
crashed with signal 11 ( 128 + 11 ) Segmentation Fault so
perhaps you have some other kind of problems? like a faulty machine?
On Tue, Jun 18, 2002 at 01:40:56AM -0500, Felipe Contreras wrote:
> Hi,
>
> I have this problem when running 2.5.22, make can't run itself inside a
> Makefile.
>
> Let's say I have this Makefile:
> test:
> ( make -v )
>
> It fails saying this:
> ( make -v )
> make: *** [test] Error 139
>
> I don't have any idea about what can be causing this error, might be something
> to do with reiserfs...
>
> Any ideas?
>
> --
> Felipe Contreras
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Teo
On Tue, Jun 18, 2002 at 09:45:26AM +0300, Teodor Iacob wrote:
> 139 return code means that the process that make was running
> crashed with signal 11 ( 128 + 11 ) Segmentation Fault so
> perhaps you have some other kind of problems? like a faulty machine?
If you consider a "faulty machine" a development one, then yes, I have one. I
have glibc-2.2.5 gcc-3.1 linux-2.5.23, but that shouldn't matter I want to know
what's causing this and I'll like to fix it.
I'm pretty sure this started with linux-2.5.19, might be it has something to do
with forking, might be it's a make bug, but I think something is wrong here.
--
Felipe Contreras