Hyperion Entertainment Message Boards

@samo79

In general, "make" is pure command. So, pure command can not works only if it can't loads (broken file or so). You can just do that:

ram:> which make
ram:> make

And see, what will happens. If after you just type make , without any sources. It should be something like:
If it will be like this, then make works. If not, and you will have your usual freeze, then time to check heavy what happens : run snoopy , and so on. Maybe your unix-kind tools borks somehow (like bash, etc). Maybe you overwrite something in system somehow. All kind of weirdos can happens.

@Alfkil

Alfkil wrote:What does it say if you type "which make" or "which gmake" in a shell?

The "which make" and "which gmake" command give me the path normally, however if i type "make" or "gmake" instead to have a message (or a compile output of course) i have a system freeze, more details below ..

@kas1e

kas1e wrote:In general, "make" is pure command. So, pure command can not works only if it can't loads (broken file or so). You can just do that:

ram:> which make
ram:> make

The "which make" seems fine and give me the path of when the command actually reside
So (as i have currently reinstalled the entire SDK also into another place for this test) it's currently that:

Processo: Shell 4
4.AmigaOS4:> which make
Work:SDK_2/SDK/C/make
4.AmigaOS4:>

Then at this point if i type "make" --> nothing happen and the shell does not respond anymore (Workbench will freeze aswell)

kas1e wrote:And see, what will happens. If after you just type make , without any sources. It should be something like:

Code: Select all

ram:> which make
Work:SDK/C/make
ram:> list Work:SDK/C/make
342008
ram:> Work:SDK/c/make
make: *** No targets specified and no makefile found. Stop.

Infact, typing "make" without anything should give me the "No target specified blabla" message, instead it freeze my system exactly there

kas1e wrote:If it will be like this, then make works. If not, and you will have your usual freeze, then time to check heavy what happens : run snoopy , and so on. Maybe your unix-kind tools borks somehow (like bash, etc). Maybe you overwrite something in system somehow. All kind of weirdos can happens.

Yep most probably somethings broken still on my system, here my Snoopy output, the log was taken during the entire procedure (opening the shell, typing the various command etc until the freeze)

http://www.sendspace.com/file/kzpelf

What about stacksize?

Best regards,

Niels

nbache wrote:What about stacksize?

Best regards,

Niels

On the "make" icon i have this stack --> 32768

samo79 wrote:On the "make" icon i have this stack --> 32768

That doesn't sound like very much. Try putting a zero behind it for a start.

Best regards,

Niels

It's the same even increasing the stack ..
At this point i wait if someone can help me understanding the (Snoopy) log, in alternative i will do a quick format !

The Snoopy log isnt telling much about "make". It tells that "make" is just running fine

The astonishing part of the log is the listing of your "AppDir:" contents. I dont know where it originates from, it follows the "make" invocation directly, but it shouldnt. To me it seems that there is another executable doing strange things with "env-handler". Might be that this leads to the "freeze" you described here. I put "freeze" in double quotes here, because there is a slight chance that this isnt a "freeze" at all, but dos.library-debug-output "hitting the brake". You should check the debug output, too (using serial connection or Sashimi). There is something strange going on with your system.

whose wrote:The Snoopy log isnt telling much about "make". It tells that "make" is just running fine

The astonishing part of the log is the listing of your "AppDir:" contents. I dont know where it originates from, it follows the "make" invocation directly, but it shouldnt.

Isn't that just env-handler itself, setting itself up by copying everything relevant from ENVARC: to ENV:?

Not sure, but that was my thought when I saw it in his log.

Best regards,

Niels

@all

Well, at the end i just formatted the entire partition and i reinstalled AmigaOS from scratch, this solve the issue
Thanks for the help guys