Re: Does splint work for anyone?

2024-02-16 Thread Stephen Smoogen 
On Fri, 16 Feb 2024 at 10:51, David Cantrell  wrote:

> On 2/15/24 11:19, Stephen Smoogen wrote:
> >
> >
> > On Thu, 15 Feb 2024 at 10:15, David Cantrell  > > wrote:
> >
> > On 2/14/24 13:32, Stephen Smoogen wrote:
> >  >
> >  >
> >  > On Fri, 9 Feb 2024 at 17:17, Ian Laurie  > 
> >  > >> wrote:
> >  >
> >  > On 2/10/24 05:06, Stephen Smoogen wrote:
> >  > >
> >  > > I was trying out the splint program on some code and found
> > that it
> >  > > doesn't seem to work on any recent release due to changes
> > in various
> >  > > header files
> >  > I tried using splint many years ago in connection with
> embedded
> >  > programming, and even though the GCC based embedded compiler
> > I was using
> >  > was several major version numbers behind what was natively in
> > Fedora, I
> >  > found splint to be hopelessly behind the times and utterly
> > unusable.  I
> >  > don't know why it is even packaged in Fedora.
> >  >
> >  > I wish I had the skills necessary to bring it up to date but
> > I don't.
> >  >
> >  >
> >  > Me too. I saw it is FTBFS in F40 and added my data
> >  > to https://bugzilla.redhat.com/show_bug.cgi?id=2261709
> > 
> >  >  > >
> >
> > I got it building and posted a PR:
> > https://src.fedoraproject.org/rpms/splint/pull-request/1
> > 
> >
> > The upstream project went dormant in 2010, but there are some other
> > semi-active forks.  I don't think that really matters.  The program
> > itself could be useful for research and just as another tool in the
> > toolbox for development.
> >
> >
> > Does it "work?" however.
> > ```
> > [ssmoogen@toolbox phytool (fix_asprintf)]$ splint +posixlib phytool.c
> > Splint 3.1.2 --- 22 Jul 2023
> >
> > /usr/include/asm-generic/int-ll64.h:20:24: Parse Error:
> >  Suspect missing struct or union keyword: __signed__ :
> >  int. (For help on parse errors, see splint -help parseerrors.)
> > *** Cannot continue.
> > ```
> >
> > Trying different flags, just got it to find even more 'parseerrors' on
> > more and more layers of header files. I could not find any combination
> > of flags which didn't result in the program not working with how our
> > headers are done in post Fedora 38 (my oldest system).
>
> It depends on what you mean by "work".  It's definitely clear there is a
> lot of syntax it does not understand.
>
>
It was mainly that I couldn't get it to 'parse' various simple C code
without bombing out over standard headers it couldn't parse. I was mainly
asking in case you had a standard flag set which made it work and I had
missed the obvious.


> There is at least one fork I found on github that has continued work on
> splint, but its most recent commit is from 3 years ago and it has open
> issues like "support C99 syntax".
>
>
Yeah I could not get the one I found to compile (but it was even older) so
not sure where things stood in forks either.


> splint's days may be over.
>
>
I will pour one compile out for it.


> --
> David Cantrell 
> Red Hat, Inc. | Boston, MA | EST5EDT
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Does splint work for anyone?

2024-02-16 Thread David Cantrell 

On 2/15/24 11:19, Stephen Smoogen wrote:



On Thu, 15 Feb 2024 at 10:15, David Cantrell > wrote:


On 2/14/24 13:32, Stephen Smoogen wrote:
 >
 >
 > On Fri, 9 Feb 2024 at 17:17, Ian Laurie mailto:nixu...@mail.com>
 > >> wrote:
 >
 >     On 2/10/24 05:06, Stephen Smoogen wrote:
 >     >
 >     > I was trying out the splint program on some code and found
that it
 >     > doesn't seem to work on any recent release due to changes
in various
 >     > header files
 >     I tried using splint many years ago in connection with embedded
 >     programming, and even though the GCC based embedded compiler
I was using
 >     was several major version numbers behind what was natively in
Fedora, I
 >     found splint to be hopelessly behind the times and utterly
unusable.  I
 >     don't know why it is even packaged in Fedora.
 >
 >     I wish I had the skills necessary to bring it up to date but
I don't.
 >
 >
 > Me too. I saw it is FTBFS in F40 and added my data
 > to https://bugzilla.redhat.com/show_bug.cgi?id=2261709

 > >

I got it building and posted a PR:
https://src.fedoraproject.org/rpms/splint/pull-request/1


The upstream project went dormant in 2010, but there are some other
semi-active forks.  I don't think that really matters.  The program
itself could be useful for research and just as another tool in the
toolbox for development.


Does it "work?" however.
```
[ssmoogen@toolbox phytool (fix_asprintf)]$ splint +posixlib phytool.c
Splint 3.1.2 --- 22 Jul 2023

/usr/include/asm-generic/int-ll64.h:20:24: Parse Error:
     Suspect missing struct or union keyword: __signed__ :
     int. (For help on parse errors, see splint -help parseerrors.)
*** Cannot continue.
```

Trying different flags, just got it to find even more 'parseerrors' on 
more and more layers of header files. I could not find any combination 
of flags which didn't result in the program not working with how our 
headers are done in post Fedora 38 (my oldest system).


It depends on what you mean by "work".  It's definitely clear there is a 
lot of syntax it does not understand.


There is at least one fork I found on github that has continued work on 
splint, but its most recent commit is from 3 years ago and it has open 
issues like "support C99 syntax".


splint's days may be over.

--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Does splint work for anyone?

2024-02-15 Thread Stephen Smoogen 
On Thu, 15 Feb 2024 at 10:15, David Cantrell  wrote:

> On 2/14/24 13:32, Stephen Smoogen wrote:
> >
> >
> > On Fri, 9 Feb 2024 at 17:17, Ian Laurie  > > wrote:
> >
> > On 2/10/24 05:06, Stephen Smoogen wrote:
> > >
> > > I was trying out the splint program on some code and found that it
> > > doesn't seem to work on any recent release due to changes in
> various
> > > header files
> > I tried using splint many years ago in connection with embedded
> > programming, and even though the GCC based embedded compiler I was
> using
> > was several major version numbers behind what was natively in
> Fedora, I
> > found splint to be hopelessly behind the times and utterly
> unusable.  I
> > don't know why it is even packaged in Fedora.
> >
> > I wish I had the skills necessary to bring it up to date but I don't.
> >
> >
> > Me too. I saw it is FTBFS in F40 and added my data
> > to https://bugzilla.redhat.com/show_bug.cgi?id=2261709
> > 
>
> I got it building and posted a PR:
> https://src.fedoraproject.org/rpms/splint/pull-request/1
>
> The upstream project went dormant in 2010, but there are some other
> semi-active forks.  I don't think that really matters.  The program
> itself could be useful for research and just as another tool in the
> toolbox for development.
>
>
Does it "work?" however.
```
[ssmoogen@toolbox phytool (fix_asprintf)]$ splint +posixlib phytool.c
Splint 3.1.2 --- 22 Jul 2023

/usr/include/asm-generic/int-ll64.h:20:24: Parse Error:
Suspect missing struct or union keyword: __signed__ :
int. (For help on parse errors, see splint -help parseerrors.)
*** Cannot continue.
```

Trying different flags, just got it to find even more 'parseerrors' on more
and more layers of header files. I could not find any combination of flags
which didn't result in the program not working with how our headers are
done in post Fedora 38 (my oldest system).



> --
> David Cantrell 
> Red Hat, Inc. | Boston, MA | EST5EDT
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Does splint work for anyone?

2024-02-15 Thread David Cantrell 
On 2/14/24 13:32, Stephen Smoogen wrote:
> 
> 
> On Fri, 9 Feb 2024 at 17:17, Ian Laurie  > wrote:
> 
> On 2/10/24 05:06, Stephen Smoogen wrote:
> >
> > I was trying out the splint program on some code and found that it
> > doesn't seem to work on any recent release due to changes in various
> > header files
> I tried using splint many years ago in connection with embedded
> programming, and even though the GCC based embedded compiler I was using
> was several major version numbers behind what was natively in Fedora, I
> found splint to be hopelessly behind the times and utterly unusable.  I
> don't know why it is even packaged in Fedora.
> 
> I wish I had the skills necessary to bring it up to date but I don't.
> 
> 
> Me too. I saw it is FTBFS in F40 and added my data
> to https://bugzilla.redhat.com/show_bug.cgi?id=2261709
> 

I got it building and posted a PR:
https://src.fedoraproject.org/rpms/splint/pull-request/1

The upstream project went dormant in 2010, but there are some other
semi-active forks.  I don't think that really matters.  The program
itself could be useful for research and just as another tool in the
toolbox for development.

-- 
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Does splint work for anyone?

2024-02-14 Thread Stephen Smoogen 
On Fri, 9 Feb 2024 at 17:17, Ian Laurie  wrote:

> On 2/10/24 05:06, Stephen Smoogen wrote:
> >
> > I was trying out the splint program on some code and found that it
> > doesn't seem to work on any recent release due to changes in various
> > header files
> I tried using splint many years ago in connection with embedded
> programming, and even though the GCC based embedded compiler I was using
> was several major version numbers behind what was natively in Fedora, I
> found splint to be hopelessly behind the times and utterly unusable.  I
> don't know why it is even packaged in Fedora.
>
> I wish I had the skills necessary to bring it up to date but I don't.
>
>
Me too. I saw it is FTBFS in F40 and added my data to
https://bugzilla.redhat.com/show_bug.cgi?id=2261709



> --
> Ian Laurie
> FAS: nixuser | IRC: nixuser
> TZ: Australia/Sydney
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Does splint work for anyone?

2024-02-09 Thread Ian Laurie 

On 2/10/24 05:06, Stephen Smoogen wrote:


I was trying out the splint program on some code and found that it
doesn't seem to work on any recent release due to changes in various
header files

I tried using splint many years ago in connection with embedded
programming, and even though the GCC based embedded compiler I was using
was several major version numbers behind what was natively in Fedora, I
found splint to be hopelessly behind the times and utterly unusable.  I
don't know why it is even packaged in Fedora.

I wish I had the skills necessary to bring it up to date but I don't.

--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Does splint work for anyone?

2024-02-09 Thread Stephen Smoogen 
I was trying out the splint program on some code and found that it doesn't
seem to work on any recent release due to changes in various header files
```
[ssmoogen@toolbox phytool (fix_asprintf)]$ splint +posixlib phytool.c
Splint 3.1.2 --- 22 Jul 2023

/usr/include/asm-generic/int-ll64.h:20:24: Parse Error:
Suspect missing struct or union keyword: __signed__ :
int. (For help on parse errors, see splint -help parseerrors.)
*** Cannot continue.
```

I haven't figured out a set of flags to get past this to make the tool
work. I looked upstream and the site has a 'we are no longer working on
this tool'. So I am not sure if the software 'works', 'how to fix the
software', or 'did I miss something obvious and everyone else knows this
one trick'.

Thanks for any help.

-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue