Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Ronald Newsgroups: comp.sys.acorn.programmer Subject: Re: GCC4 directory/extension names Date: Mon, 11 Mar 2019 11:45:49 +1300 Organization: - Lines: 28 Message-ID: <6b13c79257.beeb@-.-> References: <27o*PW-hx@news.chiark.greenend.org.uk> <3feab39257.druck@druck.org.uk> Injection-Info: reader02.eternal-september.org; posting-host="ab0f7f9856562d30e5cb3143ab12470e"; logging-data="2626"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX186jFP6ZRSJE3Cwx8JCc9hT" User-Agent: Messenger-Pro/1.00c (MsgServe/1.00a) (RISC-OS/5.24) NewsHound/v1.50-32 Cancel-Lock: sha1:ha44zm9tMWBmFM7j1E6AA4r9Ri8= Xref: csiph.com comp.sys.acorn.programmer:5714 In message Theo wrote: > druck wrote: > > But that didn't work, it still didn't recognise #include "something.hpp" > > I tried gcc$env$sfix to, but looking in !SharedLibs.libs.libunixlib > > "UnixEnv$appname$sfix" is the correct variable name. > > Since it's the preprocessor reading the header files, you might need to set > UnixEnv$cpp$sfix - I don't know if that's set by the !Run file? > > Theo I thought gcc was the frontend for everything it does thereafter. I recall making UnixEnv$ changes sometimes required a reboot to get the true result. There is a build file for gcc with the riscosify list, I think it was to do with libscl though. You may also get through it with the ? wild card as long as there is no similar .h files. Lastly, I have a !GCC built without riscosification so norcroft source code has to be flattened to resemble linux files, or standard source files just work. That usually fixes any naming problems. I could upload it to my GoogleDrive I guess. Ronald