> On 30 Nov 2025, at 19:13, Ranjan Maitra via users
> <[email protected]> wrote:
>
> Barry,
>
> Thanks very much for this!
>
>
> On Sun Nov30'25 04:20:06PM, Barry Scott wrote:
>> From: Barry Scott <[email protected]>
>> Date: Sun, 30 Nov 2025 16:20:06 +0000
>> To: Community support for Fedora users <[email protected]>
>> CC: Ranjan Maitra <[email protected]>
>> Reply-To: Community support for Fedora users <[email protected]>
>> Subject: Re: OT: rpmbuild SPEC error
>>
>>
>>
>>> On 27 Nov 2025, at 15:29, Ranjan Maitra via users
>>> <[email protected]> wrote:
>>>
>>> Hi,
>>>
>>> I posted this twice earlier, but it did not show up because the error
>>> message it moving it a tad more than 60KB which makes it require moderator
>>> approval (which may well be delayed because of the holiday weekend in the
>>> US). So, here is a repost. Hopefully, someone can get to it before the
>>> 24-hour clock on the fpaste runs out (I do not see how to increase that
>>> time.)
>>>
>>>
>>> I am the package maintainer of SLiM, the Simple Login Manager. While trying
>>> to take care of an automated BZ request, I decided to look into also
>>> updating the package.
>>>
>>> Because upstream is not very responsive, as the author is sadly indisposed
>>> for the long-term, I moved the code to github at
>>> https://github.com/maitra/slim-fork after having made some of the
>>> corrections (suggested earlier here) which make the package compile without
>>> error. And also bumped up the cmakeminimum which is what triggered the BZ
>>> request.
>>>
>>> However, when I go to build the RPM with the spec file, I get an error.
>>>
>>> THe spec file is here: https://paste.centos.org/view/96e6b7db
>>
>> No longer a live link
>
> Yes, sadly so, because of the 23:59 limit at paste.centos.org
> <http://paste.centos.org/>. Uploading now.
>
> $ fpaste slim.spec
> Uploading (20.0KiB)...
> https://paste.centos.org/view/ae7eedab
Don't think you need this:
BuildRequires: systemd
Or xterm
BuildRequires: scrot xterm freeglut-devel libXrandr-devel
The rest seems okay at first glance.
I personally put each BuildRequire item on its own line.
Then when you add or remove a BUildRequire its a one line change in diff.
Having multiple items per line makes git diff harder to read in my opinion.
>
>>
>>>
>>> However, I get an error which does not show up when I do the compilation
>>> outside the spec file, which is really perplexing to me so my guess is that
>>> the problem is with the spec file, and I wonder if anyone more knowledgable
>>> on SPEC files can give me some suggestions.
>>>
>>> Here are the errors I get when I run rpmbuild -bb slim.spec.
>>>
>>> https://paste.centos.org/view/8f71e2c5
>>
>
> Now at:
>
> Uploading (83.8KiB)...
> https://paste.centos.org/view/97a6fc4a
This is the important part of the errors.
In file included from
/home/localuser/rpmbuild/BUILD/slim-fork-1.4.2-build/slim-fork-1.4.2/app.cpp:31:
/home/localuser/rpmbuild/BUILD/slim-fork-2.4.2-build/slim-fork-1.4.2/log.h:
In instantiation of ‘LogUnit& LogUnit::operator<<(const Type&) [with Type =
PAM::Exception]’:
/home/localuser/rpmbuild/BUILD/slim-fork-2.4.2-build/slim-fork-1.4.2/app.cpp:331:35:
required from here
330 | logStream << APPNAME << ": " << e << endl;
| ^
/home/localuser/rpmbuild/BUILD/slim-fork-2.4.2-build/slim-fork-1.4.2/log.h:34:25:
error: no match for ‘operator<<’ (operand types are ‘std::ostream’ {aka
‘std::basic_ostream<char>’} and ‘const PAM::Exception’)
33 | *logOut << text; logOut->flush();
| ~~~~~~~~^~~~~~~
You are missing the definition of operator<<(const PAM::Exception) - I think.
If you see it build sometimes that suggests that cmake is auto configuring to
use different header files
in the case of things build vs. when they fail.
>
>>
>> Where are you doing the builds, Fedora Koji. Copr or just local to your PC?
>>
>
> Right now, just local to my PC. I have forgotten: don't I need to have a
> working SRPM to upload to koji? Perhaps not.
You can use `mock` locally to test your srpm works in a clean environment.
See `man mock` for command line options.
This will eliminate issues with RPMs you do or do not have installed on your
system
that change the build.
Once you have a SRPM then you could build it in the copr service.
You can only use koji if you are a fedora packager.
>
> Anyway, thanks again for your response! Perhaps the error messages can shed
> some light (along with the SPEC file).
Good luck.
>
> Best wishes,
> Ranjan
> --
> _______________________________________________
> users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
