WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: libconfuse-dev.tcz: bugs in TCL14.x x86_64  (Read 1187 times)

Offline GNUser

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 1378
libconfuse-dev.tcz: bugs in TCL14.x x86_64
« on: May 02, 2023, 02:22:19 PM »
This extension has two bugs:

1. It needs a .dep file that lists libconfuse.tcz as a dependency

2. /usr/local/lib/pkgconfig/libconfuse.pc contains this line
Code: [Select]
Cflags: -I${includedir}
which should be corrected to this:
Code: [Select]
Cflags: -I${includedir}/confuse

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11316
Re: libconfuse-dev.tcz: bugs in TCL14.x x86_64
« Reply #1 on: May 02, 2023, 05:25:19 PM »
Hi GNUser
... 1. It needs a .dep file that lists libconfuse.tcz as a dependency ...
I'm afraid my feeble brain can not figure this out with the supplied information.
i3status.tcz.dep  and  tilda.tcz.dep  depend on  libconfuse.tcz.
Nothing depends on  libconfuse-dev.tcz.
libconfuse.tcz  and  libconfuse-dev.tcz  list no dependencies.

By the way, if A depends on C, and B depends on C, A can still include B as a dependency.

Offline GNUser

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 1378
Re: libconfuse-dev.tcz: bugs in TCL14.x x86_64
« Reply #2 on: May 02, 2023, 06:08:02 PM »
Hi Rich. I loaded  libconfuse-dev.tcz  to compile something that depends on libconfuse. I was surprised at compilation time with errors saying that libconfuse could not be found.

As a general rule--both in TCL as well as in other distros--loading/installing foo-dev should automatically bring in foo as well.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11316
Re: libconfuse-dev.tcz: bugs in TCL14.x x86_64
« Reply #3 on: May 02, 2023, 08:22:37 PM »
Hi GNUser
OK, now I understand what you meant.

.dep  file added.
libconfuse.pc  corrected.

Offline GNUser

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 1378
Re: libconfuse-dev.tcz: bugs in TCL14.x x86_64
« Reply #4 on: May 03, 2023, 09:50:48 AM »
Hi Rich. Thank you.