Kernel changes using SAM

[Ian Warner]

stape is back in /build/system
I could not find the patch listed, it must be
part of a larger patch set. I did a chmod of the affected files and check_patches reported no errors.
nflocks is back to its initial value
patch assesment says I am up to date.

Ian (increasingly desperate)

[Ian Warner]

I don't know if this means anything, but if I run /usr/sbin/config -c conf.SAM.c -l \ config.SAM.mk /stand/build/system.SAM
as root, the kernel compiles, but if I run the same command in /stand/build/, I get the error.

Ian

[Eric Antunes]

And with SAM (SAM -> are you able to Process the Kernel?

[Ian Warner]

No, I get the same error as always.

Ian

[Stephen Keane]

If you rename conf.SAM.c to something else (not ending in c) then run the configure command again, does that work?

[Ian Warner]

No difference.

Ian

[Eric Antunes · Accepted solution]

cp /stand/build/system.SAM stand/build/system.SAM.BAK

cp /stand/system /stand/build/system.SAM

Go to SAM and process kernel...

[Stephen Keane]

If you run

/usr/sbin/config -c conf.SAM.c -l \ config.SAM.mk /stand/build/system.SAM

but not in the /stand/build directory, it works? I see conf.SAM.c and config.SAM.mk don't have a leading path (or was that a typo?) so they would be created in whatever directory you were in at the time? If so, can you copy them into /stand/build to replace the existing ones. I've attached an ll -R of my /stand directory so you can check ownership and permissions.

[Ian Warner]

Eric, no change

Stephen, no change

Ian

[Florian Heigl (new acc)]

Just a short thing - You *should* get the whole patch list with /usr/contrib/bin/show_patches

swlist -l file > /tmp/filelist also shows file vs. patch updates.

else - I don't have a good guess. Just, that something stupid sits around in /usr/conf or whereever :)

[Ian Warner]

I got it!!!!!!!!!!

I did the changes again (poperly) this time and the kernel compiled.


Thanks to all of you who helped.

A very grateful Ian Warner