Re: [gccsdk] Is it time for a new version of GCC4?

On Tue, 30 Jun 2020, alan buckley wrote:

> Unfortunately RISC OS 5 doesn't put the modules.400 directory in it's path.

It should do. However Sys$Path is built on startup based on which
directories are actually present, so if you add a new directory you'll
need to restart the machine (or re-run !System.!Run) to get it to detect
it.

I note that the sysmerge plugin in Configure doesn't update Sys$Path, so
that's probably something we should fix. Likewise, PackMan could be taught
to re-run !System if it's created a new OS version folder.

Cheers,

- Jeffrey

Re: [gccsdk] Is it time for a new version of GCC4?

Lee Noar wrote on  23 June 2020 12:17:

 

> On 23/06/2020 07:57, alan buckley wrote:
>> Lee Noar <mailto:lee.noar@sky.com> wrote on 19 June 2020 20:53
>>
>>> I see ARMEABISupport is in the Modules.500 directory, is this then not
>>> used for RISC OS 4?
>>  
>>Well, technically no and GCC 4 doesn't use it anyway. It's really meant
>>for GCC 8 and newer, which I didn't really envision being used on RISC
>>OS 4 due to a 32 bit requirement.
>>However, having said that !SharedLibs.SOMRun1st loads it, so it does
>>>need to be present.
> >
> > Do we need to install it to a different Modules directory? GCC seems
>>  to need it to run at all on RISC OS 4.

> Yes, I think perhaps we should move it to the 400 directory, I'll
> have a look at doing this later on today.

Unfortunately RISC OS 5 doesn't put the modules.400 directory in it's path.

Is there any reason it can't be put in the Modules.310 directory? If SharedULib

depends on it then that's really where it should be.

 

Regards,

Alan

Mac Download?

Hi.   I don't see Mac OS listed in the downloads.  Am I SOL?

Thanks,,,

gavin

_____________________________________

Re: [gccsdk] Is it time for a new version of GCC4?

On 23/06/2020 07:57, alan buckley wrote:
> Lee Noar <mailto:lee.noar@sky.com> wrote on 19 June 2020 20:53
>
> >> I see ARMEABISupport is in the Modules.500 directory, is this then not
> >> used for RISC OS 4?
>
> >Well, technically no and GCC 4 doesn't use it anyway. It's really meant
> >for GCC 8 and newer, which I didn't really envision being used on RISC
> >OS 4 due to a 32 bit requirement.
> >However, having said that !SharedLibs.SOMRun1st loads it, so it does
> >need to be present.
>
> Do we need to install it to a different Modules directory? GCC seems
> to need it to run at all on RISC OS 4.

Yes, I think perhaps we should move it to the 400 directory, I'll
have a look at doing this later on today.

Lee.

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [gccsdk] Is it time for a new version of GCC4?

In message <DB7PR01MB49199E77DD1005248A20AFA5F0970@DB7PR01MB4919.eurpr
d01.prod.exchangelabs.com>
alan buckley <alan_baa@hotmail.com> wrote:

[snip]

> GCC also crashed on RISC OS 4 on RPCEmu when attempting to compile
> the examples.

[snip]

> I couldn't compile on RISC OS 5 as it wasn't finding the headers, but that
> could be a packaging problem. I'll check again once I do a full rebuild.

FWIW I have built gcc4 r7325 on Ubuntu 20.04.

The packaging is updated for release 4 but there remain two instances
of "Release 3" within !GCC itself.

gccsdk/gcc4/riscos/dist/!GCC/!Boot,feb

gccsdk/gcc4/Makefile at lines 23 & 24.

The examples built on RPCEmu OS4.02 here once 'make' had been built
and ARMEABISupport loaded. Also tested on the Titanium.

HTH.
--
David Pitt
Titanium

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [gccsdk] Is it time for a new version of GCC4?

Lee Noar wrote on 19 June 2020 20:53

>> I see ARMEABISupport is in the Modules.500 directory, is this then not
>> used for RISC OS 4?

>Well, technically no and GCC 4 doesn't use it anyway. It's really meant
>for GCC 8 and newer, which I didn't really envision being used on RISC
>OS 4 due to a 32 bit requirement.
>However, having said that !SharedLibs.SOMRun1st loads it, so it does
>need to be present.

 

Do we need to install it to a different Modules directory? GCC seems

to need it to run at all on RISC OS 4.

 

GCC also crashed on RISC OS 4 on RPCEmu when attempting to compile

the examples.

>> Once I�ve sorted this out and the select patch is updated I�ll have a go
>> at building a new GCC release unless someone tells me to wait a little
>> longer.

> I've been running Iris with the updated select patch for a week or two
> now and I don't see any ill effects, so I'll commit the change tomorrow.

Thanks for submitting the patch. I just need to find time to rebuild GCC

again on a different machine as the old laptop I was using is a bit flaky.

 

I couldn't compile on RISC OS 5 as it wasn't finding the headers, but that

could be a packaging problem. I'll check again once I do a full rebuild.

 

Regards,

Alan

Re: [gccsdk] DeskLib and GCCSDK

On 21/06/2020 14:31, Steve Fryatt wrote:
> On 19 Jun, Ben Avison wrote in message
> <6eb7a519-0e1e-36c0-7f9e-9433974db35a@riscosopen.org>:
>
>> On 18/06/2020 17:56, Steve Fryatt wrote:
>>> Just a followup question to this: is anyone maintaining DeskLib and
>>> curating changes?
>>
>> As far as I'm aware, it's still Philip Ludlam.
>
> I can't find Philip's name anywhere in the source or docs, so I'm not sure
> that he's even been involved?

Sorry, I was getting Desk and DeskLib muddled up - I checked, and it's
Desk that Philip maintains. The two projects forked may years ago.
Philip's website seems to be broken most of the time, but I dredged this
up from archive.org:

https://web.archive.org/web/20080515070703/http://www.philipnet.com/project/desk

Ben

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK