On 2022-10-07 at 19:27, Greg Wooledge wrote: > On Fri, Oct 07, 2022 at 07:11:51PM -0400, The Wanderer wrote: > >>> First question: do you have the relevant -dev package installed? >> >> $ apt-file search object.h | grep '/object\.h$' | grep sigc | wc -l >> 0 >> >> I suspect that that may not be a relevant question in this case; >> it doesn't look like the relevant -dev package contains that file >> (anymore). Unless the package is available in some other repo, such >> that this search wouldn't find it; I have stable and testing >> enabled, but not unstable or oldstable or experimental or anything >> of the sort. > > I did a search of oldstable on packages.debian.org and it's not > there either. I'm guessing it's something that existed in an older > version of this development package, and has been deprecated. > > You would need at least a decent understanding of this libsigc++ > package to know for sure. > > Just for grins, what happens if you comment out that #include? Maybe > the functions/whatever which used to be defined in this header file > are already being defined somewhere else. Unless I'm misunderstanding, that's already been addressed, in the original post: >>> Removing the #<include> from the offending module only caused a >>> slew of other errors. > Hey, you might get lucky. > >> What would need to be done here is to update the codebase of that >> older program to work with the updated API (etc.) of the newer >> libsigc++. > > If you *don't* get lucky, then it's this. That being why I went to this first. The only other option would be to somehow install an older (still-compatible) version of libsigc++ in a way which not only works, but doesn't conflict or interfere with the modern installed libraries. Given that libraries can have dependencies on each other, this might well not just be as simple as getting the source for the older version and compiling it (either directly, or into a revised source package which installs to names and/or paths which won't conflict); you might have to also build and install older versions of other libraries, and that could cascade. It's likely to be simpler by far to just update the program source to work with the newer version of the library, or even to not need the library at all. (For the record: it looks like I was wrong, and we *have* been told what the program involved is. I managed to forget that part of the original post by the time I wrote my reply to a reply.) -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature