Re: trinity's version of "identify"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, May  9, 2023 at 13:29 (-0700), Mike Bird via tde-users wrote:

> On Tue May 9 2023 12:28:13 Jim via tde-users wrote:
>>> I can't find a TDE "identify" program.  Can you tell me where you are
>>> finding it please?

>> Mine is in /opt/trinity/bin/identify.

>> The build scripts for Slackware put the TDE stuff either in /opt/trinity or
>> in /opt/tde, at the option of the person building it.

>> Your question makes me wonder whether the pre-built Debian packages install
>> TDE under /usr or under /opt.

> For Debian and Ubuntu the pre-built packages install TDE in /opt/trinity.

Thanks.

>> If you have the "locate" program running on your system you could also try
>> locate bin/identify
>> and see how many matching files it comes up with.

> I've searched several ways and have not yet found an "identify" in TDE.

I got it as part of tdelibkdcraw

> When was your /opt/trinity/bin/identify created?  Does this match your
> other TDE executables?

It was created about the same time (+/- a few seconds) as a bunch of other
executables.

> What is the output of running "ldd /opt/trinity/bin/identify"?

	linux-vdso.so.1 (0x00007ffc73be9000)
	liblcms2.so.2 => /usr/lib64/liblcms2.so.2 (0x00007fca2fd2e000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fca2fa00000)
	libm.so.6 => /lib64/libm.so.6 (0x00007fca2f8b8000)
	libomp.so => /usr/lib64/libomp.so (0x00007fca2fc4e000)
	libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007fca2fc33000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fca2fc12000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fca2f6d9000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fca2fdea000)
	librt.so.1 => /lib64/librt.so.1 (0x00007fca2f6cf000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007fca2f6ca000)

The list for my /usr/bin/identify is much longer (46 lines).

> Can you tell the main source file from which your
> /opt/trinity/bin/identify was built?

Looking at the build log, I see some compiler warnings from
        libkdcraw-trinity-14.1.0/libkdcraw/libraw/samples/identify.c

Given the lack of other people seeing this, I am beginning to guess it is
an issue with the Slackware build scripts, although I don't know why
Slackware would include (alleged) TDE programs that aren't used in the
Debian/Ubuntu packages.

So thanks for your responses, I think I should probably go and talk to the
guy who creates the Slackware build scripts.

                                Jim
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx



[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux