Re: [gccsdk] Is there activity here?

[alan buckley]

Theo Markettos wrote on 30 June 2017 11:28

[snip]

> Are you measuring activity by mail, or by programming?

> In the latter case, I don't have a lot of time these days but various things
> I've been doing:

> 2b. I notice Debian have made a new release, which means some of our
> upstream package versions have shifted and don't build any more.  I'm not
> sure what to do about that.

I’ve noticed that as well, I had to recently change GCCSDK to point at some
old debian lists to be able to build subversion.

I think we should strive to update to the new packages and retire the old
ones. Maybe have an archive area in GCCSDK for the old versions that are
no longer updated.

I think we should also move things that will no longer build there. But only
after checking there is no way to get them to build again.

For myself, I keep trying to bring packages up to date and rebuild them so
they will work on the Raspberry Pi 3. I tend to look at things that are
mentioned on other sites to see what to look at. The problem is I have
very little time and so progress is slow.

Regards,
Alan
___
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] pthread shutdown in atexit

[Ralph Corderoy]

Hi Alan,

> I have a mysterious crash in a SDL based program when it attempts to
> do a pthread_wait in an atexit handler. The error is: pthreads:
> ***fatal error, aborting*** pthread_yield called with context
> switching disabled.
>
> My guess is this means that GCC is shutting down the threads system
> before the atexit handler is being called.

Are you calling atexit(3) before or after your initialise pthreads?  I'd
call it after as the registered functions are called in reverse order so
if pthreads is registering one itself to "shutdown" then you want that
called after yours.

Cheers, Ralph.

___
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