{"title":"NCUBE UNIX实用程序的集合","authors":"D. Tolle","doi":"10.1145/62297.62408","DOIUrl":null,"url":null,"abstract":"When we started this work, there was no C compiler available on the NCUBE. (Now there is one, from Caine, Farber, and Gordon, Inc., and it works well, but it has some restrictions on addressing, because of the underlying Intel 80286 processor, that make it unsuitable for porting certain of the UNIX utilities.) Thus we sought out a C cross-compiler, and found one from AT&T. We obtained the necessary UNIX source licenses and the sources for AT&T’s System V/iAPX286 UNIX cross-development system. That system is intended to run on a VAX running System V UNIX, but our VAX runs Ultrix, so we ported the cross-development system to Ultrix. This involved, among other things, making hybrid versions of certain UNIX utilities, hybrids with System V ancestry but adapted to run on a Berkeley UNIX file system. It was necessary to do this for lex, yacc, m4, cut, sh, and make before we were able to build the C cross-compiler and cross-linker, because, for each of these utilities, there was some small but crucial difference in behavior between the Ultrix (Berkeley UNIX) version and the System V version. Once these hybrid utilities were in place, we were able to make the cross-linker and cross-compiler","PeriodicalId":299435,"journal":{"name":"Conference on Hypercube Concurrent Computers and Applications","volume":"63 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"A collection of NCUBE UNIX utilities\",\"authors\":\"D. Tolle\",\"doi\":\"10.1145/62297.62408\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"When we started this work, there was no C compiler available on the NCUBE. (Now there is one, from Caine, Farber, and Gordon, Inc., and it works well, but it has some restrictions on addressing, because of the underlying Intel 80286 processor, that make it unsuitable for porting certain of the UNIX utilities.) Thus we sought out a C cross-compiler, and found one from AT&T. We obtained the necessary UNIX source licenses and the sources for AT&T’s System V/iAPX286 UNIX cross-development system. That system is intended to run on a VAX running System V UNIX, but our VAX runs Ultrix, so we ported the cross-development system to Ultrix. This involved, among other things, making hybrid versions of certain UNIX utilities, hybrids with System V ancestry but adapted to run on a Berkeley UNIX file system. It was necessary to do this for lex, yacc, m4, cut, sh, and make before we were able to build the C cross-compiler and cross-linker, because, for each of these utilities, there was some small but crucial difference in behavior between the Ultrix (Berkeley UNIX) version and the System V version. Once these hybrid utilities were in place, we were able to make the cross-linker and cross-compiler\",\"PeriodicalId\":299435,\"journal\":{\"name\":\"Conference on Hypercube Concurrent Computers and Applications\",\"volume\":\"63 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1900-01-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Conference on Hypercube Concurrent Computers and Applications\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/62297.62408\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Conference on Hypercube Concurrent Computers and Applications","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/62297.62408","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
摘要
当我们开始这项工作时,NCUBE上没有可用的C编译器。(现在有一个来自Caine, Farber, and Gordon, Inc.的,它工作得很好,但是由于底层的Intel 80286处理器,它在寻址方面有一些限制,这使得它不适合移植某些UNIX实用程序。)因此,我们寻找了一个C交叉编译器,并从AT&T找到了一个。我们获得了必要的UNIX源代码许可和AT&T的System V/iAPX286 UNIX交叉开发系统的源代码。该系统旨在运行在运行system V UNIX的VAX上,但我们的VAX运行Ultrix,因此我们将交叉开发系统移植到Ultrix上。这包括制作某些UNIX实用程序的混合版本,这些工具是System V祖先的混合版本,但经过调整可以在Berkeley UNIX文件系统上运行。在我们能够构建C交叉编译器和交叉链接器之前,有必要对lex、yacc、m4、cut、sh和make执行此操作,因为对于这些实用程序中的每一个,Ultrix (Berkeley UNIX)版本和System V版本在行为上存在一些微小但至关重要的差异。一旦这些混合实用程序就位,我们就能够制作交叉链接器和交叉编译器
When we started this work, there was no C compiler available on the NCUBE. (Now there is one, from Caine, Farber, and Gordon, Inc., and it works well, but it has some restrictions on addressing, because of the underlying Intel 80286 processor, that make it unsuitable for porting certain of the UNIX utilities.) Thus we sought out a C cross-compiler, and found one from AT&T. We obtained the necessary UNIX source licenses and the sources for AT&T’s System V/iAPX286 UNIX cross-development system. That system is intended to run on a VAX running System V UNIX, but our VAX runs Ultrix, so we ported the cross-development system to Ultrix. This involved, among other things, making hybrid versions of certain UNIX utilities, hybrids with System V ancestry but adapted to run on a Berkeley UNIX file system. It was necessary to do this for lex, yacc, m4, cut, sh, and make before we were able to build the C cross-compiler and cross-linker, because, for each of these utilities, there was some small but crucial difference in behavior between the Ultrix (Berkeley UNIX) version and the System V version. Once these hybrid utilities were in place, we were able to make the cross-linker and cross-compiler