ixbuild issues NS 3.3

NeXT Computer, Inc. -> NEXTSTEP / OPENSTEP Software

Title: ixbuild issues NS 3.3
Post by: mikei on March 05, 2025, 04:31:30 PM
Was installing MusicKit4.1 and it proceeded just fine until the last couple of lines of the post_install where the line:  "ixbuild -fsv -LEnglish . " is supposed to be echoed out and executed to rebuild a .index.store file.  But I got Bus Error !...

Tried this command in several other directories unrelated to MusicKit ( like the home directory for me )  Get the same Bus Error..

Then tried a completely clean NS 3.3 image, and that line worked just fine.  So it doesn't seem to be the hardware ( I even ran memory tests! ) .. but something munged in my installation which otherwise seems perfectly fine.

Finally back to the original system, I left the -LEnglish piece off .. and it worked!  Goes right through and makes an index.score file of the rtf documentions files in whatever directory I happen to run the command in.

So I have something subtle going on ( seemingly language supportwise )  and I can't put my finger on it. The other language packages ( Italian, Spanish, French, Swedish, etc ) are not installed, wouldn't think they would be needed.  Insights anyone????   

 
Title: Re: ixbuild issues NS 3.3
Post by: user217 on March 06, 2025, 12:32:04 AM
A bus error can be a lot of things! What architecture was this on—I assume you're talking about your Color Turbo slab from the other thread? We should see if it reproduces on i386.
Title: Re: ixbuild issues NS 3.3
Post by: mikei on March 10, 2025, 03:44:00 PM
Solved it! 

Did some comparison searches on my system and a clean NS 3.3 system looking for "English" since that seemed important and it turns out I was missing a directory under /NextLibrary/Readers called  English.reader which contains two files, English.domain and English.swords   Copied those on from the clean system and ixbuild now does what it's supposed to without a "bus error" ... kind of an odd thing for a program to do to just crash with bus error instead of saying "hey .. file xyz is missing !" but there it is.

That directory has probably been missing for a very long time, interesting that nothing else on the system has ever seemed to complain about those files.




Go to top  Forum index