alt.os.linux - Can't link Qtella

Author

Can't link Qtella

Erik Boerstoel

2002-09-28, 9:29 pm

I'm trying to compile and link Qtella but I do not succeed.. I managed
to create object files (.o files), but during the process of linking
countless errors occur. Apparently a library caled QT2 (?) cannot be
found. I get a lot of errors like:

Undefined reference to QString::shared_null()
Undefined reference to QTimer::start(int, bool)

Perhaps the linker cannot find the library; so I added /usr/lib /lib en
/usr/local/lib to $PATH; but that didn't help me any further.

How can check if this library has been loaded somewhere. I've got
Mandrake 8.2 BTW

Any ideas?

Thanks in advance!

Erik Boerstoel

2002-09-28, 9:29 pm

Erik Boerstoel wrote:
> I'm trying to compile and link Qtella but I do not succeed.. I managed
> to create object files (.o files), but during the process of linking
> countless errors occur. Apparently a library caled QT2 (?) cannot be
> found. I get a lot of errors like:
>
> Undefined reference to QString::shared_null()
> Undefined reference to QTimer::start(int, bool)
>
> Perhaps the linker cannot find the library; so I added /usr/lib /lib en
> /usr/local/lib to $PATH; but that didn't help me any further.
>
> How can check if this library has been loaded somewhere. I've got
> Mandrake 8.2 BTW
>
> Any ideas?
>
> Thanks in advance!
>

In this mail I talked about PATH$, of course, I meant PATH. I assigned
a value to PATH like this:

PATH="/usr/lib:/lib:/usr/local/lib ---> and so on "

Sybren

2002-09-29, 6:29 am

Erik Boerstoel wrote:
> I'm trying to compile and link Qtella but I do not succeed.. I managed
> to create object files (.o files), but during the process of linking
> countless errors occur. Apparently a library caled QT2 (?) cannot be
> found.

You're probably missing the QT2 libraries. You might want to install
qt-2*.rpm and qt-dev-2*.rpm since they will contain the files you need.

Sybren

Erik Boerstoel

2002-09-29, 6:29 am

Sybren wrote:
> Erik Boerstoel wrote:
>
>>I'm trying to compile and link Qtella but I do not succeed.. I managed
>>to create object files (.o files), but during the process of linking
>>countless errors occur. Apparently a library caled QT2 (?) cannot be
>>found.
>>
>
> You're probably missing the QT2 libraries. You might want to install
> qt-2*.rpm and qt-dev-2*.rpm since they will contain the files you need.
>
> Sybren
>
>

That is what thought too. I went to the software manager (Mandrake
only?) and searched for 'qt'. I installed several libraries, i.e. libqt2
and libqt2-devel.
But I still got the errors after installing these libraries.

However, you are talking about qt-2*.rpm and qt-dev-2*.rpm. These
packages are, according to the software manager, not on my 3 Mandrake
8.2 discs.

So where can I get them? Or is qt-2*.rpm just another name for libqt2?

Here is the description of:
- libqt2: Shared library for the Qt2 GUI toolkit
- libqt2-devel: Headers files and libraries for applications which will
use Qt2

Erik.

Sybren

2002-09-29, 7:28 am

Erik Boerstoel wrote:
> I'm trying to compile and link Qtella but I do not succeed.. I managed
> to create object files (.o files), but during the process of linking
> countless errors occur. Apparently a library caled QT2 (?) cannot be
> found.

You're probably missing the QT2 libraries. You might want to install
qt-2*.rpm and qt-dev-2*.rpm since they will contain the files you need.

Sybren

Erik Boerstoel

2002-09-29, 7:29 am

Richard Adams

2002-09-29, 7:29 am

In article <3D96F7A0.6090101@planet.nl>, "Erik Boerstoel"
<epboerstoel@planet.nl> wrote:

> However, you are talking about qt-2*.rpm and qt-dev-2*.rpm. These
> packages are, according to the software manager, not on my 3 Mandrake
> 8.2 discs.
>
> So where can I get them? Or is qt-2*.rpm just another name for libqt2?
>
> Here is the description of:
> - libqt2: Shared library for the Qt2 GUI toolkit - libqt2-devel: Headers
> files and libraries for applications which will use Qt2
>
> Erik.

Did you run 'ldconfig' after installing the new packages and before
tyring to link your new peogram, if not thats your problem.

--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

Richard Adams

2002-09-29, 8:29 am

Erik Boerstoel

2002-09-29, 8:29 am

Richard Adams wrote:
> In article <3D96F7A0.6090101@planet.nl>, "Erik Boerstoel"
> <epboerstoel@planet.nl> wrote:
>
>
>>However, you are talking about qt-2*.rpm and qt-dev-2*.rpm. These
>>packages are, according to the software manager, not on my 3 Mandrake
>>8.2 discs.
>>
>>So where can I get them? Or is qt-2*.rpm just another name for libqt2?
>>
>>Here is the description of:
>>- libqt2: Shared library for the Qt2 GUI toolkit - libqt2-devel: Headers
>>files and libraries for applications which will use Qt2
>>
>>Erik.
>>
>
> Did you run 'ldconfig' after installing the new packages and before
> tyring to link your new peogram, if not thats your problem.
>
>

Thanks for your reply. I did not run ldconfig, I installed the packages
with the software manager, that's all I did.
I'm new to Linux and I don't fully understand what ldconfig does, how do
I use this command? I've taken a look at 'man ldconfig', I understand
that this command makes libraries available (or "seen") to other
programs; so do I have type ldconfig libqt2 or so? I do not wanna go on
before I know what I am doing..

Giannis Georgalis

2002-09-29, 8:29 am

Erik Boerstoel <epboerstoel@planet.nl> writes:
> I'm new to Linux and I don't fully understand what ldconfig does, how
> do I use this command? I've taken a look at 'man ldconfig', I
> understand that this command makes libraries available (or "seen") to
> other programs;

ldconfig creates the file ld.so.cache, which is a "database"
containing the path to the system's libraries. This has the same
effect as the environment variable LD_LIBRARY_PATH. Do "man dlopen"
for more information.

> so do I have type ldconfig libqt2 or so? I do not
> wanna go on before I know what I am doing..

No, to "compile" the ld.so.conf file (and create ld.so.cache) type
just "ldconfig" as root. Or "ldconfig -v" to see all the libraries
that are loaded.

--
int main(void){int j=1234;/*(c)2002 jgeorgal */
char t[] ="<G> @abcdefghijklmnopqrstuvwxyz.\n";
char*i ="qhui<xfi.df rwgzfizjz.f rwgqqwqtigiz";
while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof
t-1),(putchar(t[j])));return 0;}/* under GPL */

Erik Boerstoel

2002-09-29, 9:29 am

Giannis Georgalis

2002-09-29, 9:29 am

Erik Boerstoel

2002-09-29, 1:29 pm

Giannis Georgalis wrote:
> Erik Boerstoel <epboerstoel@planet.nl> writes:
>
>>I'm new to Linux and I don't fully understand what ldconfig does, how
>>do I use this command? I've taken a look at 'man ldconfig', I
>>understand that this command makes libraries available (or "seen") to
>>other programs;
>>
>
> ldconfig creates the file ld.so.cache, which is a "database"
> containing the path to the system's libraries. This has the same
> effect as the environment variable LD_LIBRARY_PATH. Do "man dlopen"
> for more information.
>
>
>>so do I have type ldconfig libqt2 or so? I do not
>>wanna go on before I know what I am doing..
>>
>
> No, to "compile" the ld.so.conf file (and create ld.so.cache) type
> just "ldconfig" as root. Or "ldconfig -v" to see all the libraries
> that are loaded.
>
>

Thanks for your reply. I've done 'ldconfig', but I still get error
messages. I thinks it's clear that I haven't installed the libraries.
Neither the README nor the INSTALL told me which libraries are required.
So I'm a bit clueless now...

Sybren

2002-09-29, 1:29 pm

Richard Adams wrote:

> Did you run 'ldconfig' after installing the new packages and before
> tyring to link your new peogram, if not thats your problem.

This usually isn't needed on RPM-based systems, since the post-install
script of the RPM usually runs ldconfig for you.

Sybren

Sybren

2002-09-29, 1:29 pm

Erik Boerstoel wrote:

> Thanks for your reply. I've done 'ldconfig', but I still get error
> messages. I thinks it's clear that I haven't installed the libraries.
> Neither the README nor the INSTALL told me which libraries are required.
> So I'm a bit clueless now...

Me too. Try looking on www.rpmfind.net maybe you can find some extra RPMs
there. If not: please post the entire error message here, so that we can
read it first-hand.

Sybren

Richard Adams

2002-09-29, 1:29 pm

In article < 3d9744ca$0$1335$e4fe514c@dread
er5.news.xs4all.nl>, "Sybren"
<sybrenUSE@yourthirdtower.imagination.com> wrote:

> Richard Adams wrote:
>
>> Did you run 'ldconfig' after installing the new packages and before
>> tyring to link your new peogram, if not thats your problem.
>
> This usually isn't needed on RPM-based systems, since the post-install
> script of the RPM usually runs ldconfig for you.

Oh well, just another reason for me to stay away from RPM's then.
Long live rpm2targz, yes i use slackware.

>
> Sybren
>

--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

Sybren

2002-09-29, 1:29 pm

Richard Adams wrote:

>> This usually isn't needed on RPM-based systems, since the post-install
>> script of the RPM usually runs ldconfig for you.
>
> Oh well, just another reason for me to stay away from RPM's then.
> Long live rpm2targz, yes i use slackware.

Never tried slackware myself; I'm using Debian, and I'm quite happy with it.
I just like the idea of a file belonging to a certain package (.deb in my
case), so that I can cleanly uninstall a program / package when I want to.
Don't you miss that when you use tarballs only?

Sybren

Peter T. Breuer

2002-09-29, 1:29 pm

Erik Boerstoel <epboerstoel@planet.nl> wrote:
> Thanks for your reply. I've done 'ldconfig', but I still get error
> messages. I thinks it's clear that I haven't installed the libraries.

List the error messages. We can't help you without them ...

Peter

Richard Adams

2002-09-29, 1:30 pm

In article < 3d9747a9$0$1335$e4fe514c@dread
er5.news.xs4all.nl>, "Sybren"
<sybrenUSE@yourthirdtower.imagination.com> wrote:

> Richard Adams wrote:
>
>>> This usually isn't needed on RPM-based systems, since the post-install
>>> script of the RPM usually runs ldconfig for you.
>>
>> Oh well, just another reason for me to stay away from RPM's then. Long
>> live rpm2targz, yes i use slackware.
>
> Never tried slackware myself; I'm using Debian, and I'm quite happy with
> it. I just like the idea of a file belonging to a certain package (.deb
> in my case), so that I can cleanly uninstall a program / package when I
> want to. Don't you miss that when you use tarballs only?

NOT at all, if one uses his head, most programs have an uninstall option
thesedays, so cleaning up is of little importance.
Also on top of that, if one installs user programs they mostly go into
/usr/local so it makes it very easy to keep track of where things are.

Stop here, this thread was about something completly different.

>
> Sybren

--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

Peter T. Breuer

2002-09-29, 1:30 pm

Sybren <sybrenUSE@yourthirdtower.imagination.com> wrote:
> Richard Adams wrote:
[colo
r=darkred]
>>> This usually isn't needed on RPM-based systems, since the post-install
>>> script of the RPM usually runs ldconfig for you.
>>
>> Oh well, just another reason for me to stay away from RPM's then.
>> Long live rpm2targz, yes i use slackware.[/color]

> Never tried slackware myself; I'm using Debian, and I'm quite happy with it.
> I just like the idea of a file belonging to a certain package (.deb in my
> case), so that I can cleanly uninstall a program / package when I want to.
> Don't you miss that when you use tarballs only?

Nothing stops you knowing which tar a file comes from if you use
tarballs! I normally make a list and drop it in /var/log/packages.
But if you use a package manager on the tar, the list'll go in there
anyway.

(I never understand why people who use rpms think that they are doing
something new in that regard ...).

Peter

Erik Boerstoel

2002-09-29, 2:29 pm

Sybren

2002-09-29, 2:29 pm

Sybren

2002-09-29, 2:29 pm

Richard Adams

2002-09-29, 2:29 pm

Sybren

2002-09-29, 2:29 pm

Peter T. Breuer

2002-09-29, 2:29 pm

Richard Adams

2002-09-29, 2:29 pm

Peter T. Breuer

2002-09-29, 2:30 pm

Erik Boerstoel

2002-09-29, 3:29 pm

Sybren wrote:
> Erik Boerstoel wrote:
>
>
>>Thanks for your reply. I've done 'ldconfig', but I still get error
>>messages. I thinks it's clear that I haven't installed the libraries.
>>Neither the README nor the INSTALL told me which libraries are required.
>> So I'm a bit clueless now...
>>
>
> Me too. Try looking on www.rpmfind.net maybe you can find some extra RPMs
> there. If not: please post the entire error message here, so that we can
> read it first-hand.
>
> Sybren
>
>

Here are few of the many error messages:

/home/erik/tmp/qtella-0.4.2/src/BMergeDialog.cpp(.text+0x134a):undefined
reference to 'QString::shared_null'
/home/erik/tmp/qtella-0.4.2/src/BMergeDialog.cpp(.text+0x1359):undefined
reference to 'QStringData::deleteSelf()'
/home/erik/tmp/qtella-0.4.2/src/BMergeDialog.cpp(.text+0x1378):undefined
reference to 'QGridLayout::addWidget(QWidge
t*, int, int, int)'

This goes on and on and on.! However, everthing is related to
Q-functions (so QGridLayout, QString etc). Any idea which package
contains them?

Erik

Richard Adams

2002-09-29, 3:29 pm

In article <3D9773B2.7020608@planet.nl>, "Erik Boerstoel"
<epboerstoel@planet.nl> wrote:

> Sybren wrote:
>> Erik Boerstoel wrote:
>>
>>
>>>Thanks for your reply. I've done 'ldconfig', but I still get error
>>>messages. I thinks it's clear that I haven't installed the libraries.
>>>Neither the README nor the INSTALL told me which libraries are
>>>required.
>>> So I'm a bit clueless now...
>>>
>>>
>> Me too. Try looking on www.rpmfind.net maybe you can find some extra
>> RPMs there. If not: please post the entire error message here, so that
>> we can read it first-hand.
>>
>> Sybren
>>
>>
>>
> Here are few of the many error messages:
>
> /home/erik/tmp/qtella-0.4.2/src/BMergeDialog.cpp(.text+0x134a):undefined
> reference to 'QString::shared_null'
> /home/erik/tmp/qtella-0.4.2/src/BMergeDialog.cpp(.text+0x1359):undefined
> reference to 'QStringData::deleteSelf()'
> /home/erik/tmp/qtella-0.4.2/src/BMergeDialog.cpp(.text+0x1378):undefined
> reference to 'QGridLayout::addWidget(QWidge
t*, int, int, int)'
>
>
> This goes on and on and on.! However, everthing is related to
> Q-functions (so QGridLayout, QString etc). Any idea which package
> contains them?

At a guess, QT libs...

Your problems are at linking time, so 'ldd', dynamic linker is having
problems defining, it does not see your QT_LIBS, have you defined your
QT_DIR in your enviroment.??

Another thing which i often come upagainst when installing libs half way
thro' a compile is that problems arise like this one.
Have you tryed.
make distclean
../configure
make
make install

Just a thought, as i have not read all the mesaages on this thread.

>
> Erik

--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

Erik Boerstoel

2002-09-29, 4:29 pm

Richard Adams

2002-09-29, 4:29 pm

Erik Boerstoel

2002-09-29, 5:29 pm

Richard Adams wrote:
> In article <3D9773B2.7020608@planet.nl>, "Erik Boerstoel"
> <epboerstoel@planet.nl> wrote:
>
>
>>Sybren wrote:
>>
>>>Erik Boerstoel wrote:
>>>
>>>
>>>
>>>>Thanks for your reply. I've done 'ldconfig', but I still get error
>>>>messages. I thinks it's clear that I haven't installed the libraries.
>>>>Neither the README nor the INSTALL told me which libraries are
>>>>required.
>>>> So I'm a bit clueless now...
>>>>
>>>>
>>>>
>>>Me too. Try looking on www.rpmfind.net maybe you can find some extra
>>>RPMs there. If not: please post the entire error message here, so that
>>>we can read it first-hand.
>>>
>>>Sybren
>>>
>>>
>>>
>>>
>>Here are few of the many error messages:
>>
>>/home/erik/tmp/qtella-0.4.2/src/BMergeDialog.cpp(.text+0x134a):undefined
>>reference to 'QString::shared_null'
>>/home/erik/tmp/qtella-0.4.2/src/BMergeDialog.cpp(.text+0x1359):undefined
>>reference to 'QStringData::deleteSelf()'
>>/home/erik/tmp/qtella-0.4.2/src/BMergeDialog.cpp(.text+0x1378):undefined
>>reference to 'QGridLayout::addWidget(QWidge
t*, int, int, int)'
>>
>>
>>This goes on and on and on.! However, everthing is related to
>>Q-functions (so QGridLayout, QString etc). Any idea which package
>>contains them?
>>
>
> At a guess, QT libs...
>
> Your problems are at linking time, so 'ldd', dynamic linker is having
> problems defining, it does not see your QT_LIBS, have you defined your
> QT_DIR in your enviroment.??
>

I am a newbie, how do I check and set this variable?

> Another thing which i often come upagainst when installing libs half way
> thro' a compile is that problems arise like this one.
> Have you tryed.
> make distclean
> ./configure
> make
> make install
>

I've tried this but unfortunately, to no avail

> Just a thought, as i have not read all the mesaages on this thread.
>
>
>>Erik
>>
>

Erik Boerstoel

2002-09-29, 6:29 pm

Sybren

2002-09-30, 12:29 am

Erik Boerstoel wrote:

> Here are few of the many error messages:

Can you also post the command that is executed, that causes this list of
errors?

> This goes on and on and on.! However, everthing is related to
> Q-functions (so QGridLayout, QString etc). Any idea which package
> contains them?

That's QT. Maybe you're linking the files statically without having the
static libraries to link to? Could you give us the complete ./configure
command you're using, plus its output as well?

Sybren

Bruce Burhans

2002-09-30, 12:29 am

"Erik Boerstoel" <epboerstoel@planet.nl> wrote in message
news:3D966CC2.1050606@planet.nl...
> I'm trying to compile and link Qtella but I do not succeed.. I managed
> to create object files (.o files), but during the process of linking
> countless errors occur. Apparently a library caled QT2 (?) cannot be
> found. I get a lot of errors like:
>
> Undefined reference to QString::shared_null()
> Undefined reference to QTimer::start(int, bool)
>
> Perhaps the linker cannot find the library; so I added /usr/lib /lib en
> /usr/local/lib to $PATH; but that didn't help me any further.
>
> How can check if this library has been loaded somewhere. I've got
> Mandrake 8.2 BTW
>
> Any ideas?
>
> Thanks in advance!
>
>

as root

find / -name 'filename'

Bruce<+>

Sybren

2002-09-30, 1:29 am

Bruce Burhans

2002-09-30, 1:29 am

Faux_Pseudo

2002-09-30, 3:28 am

_.--- Bruce Burhans spoke in alt.os.linux --------._
>> How can check if this library has been loaded somewhere. I've got
>> Mandrake 8.2 BTW
>>
> as root
>
> find / -name 'filename'

Depending on how many files are on your system and the time of day
that might not be the most efficant way of doing things. If updatedb
has run since the file was put on the system (it tends to run a 04:00)
then "locate filename" is going to be much faster.

If updatedb hasn't run then it helps to narrow down the find path just
a bit based on whatever knowledge one has on the file system layout.

for lib files

,--don't forget that star
find /usr /opt /lib -name *filename -print
And you might want another * here^ depending on the name

'---...____ Faux_Pseudo ________________...---~~~

--
ICQ=66618055 : --(-<= Now Playing =>-)-- http://asciipr0n.com/fp
YIM=faux_pseudo : Rev: s_-_07_-_Think_Tank_-_Disc_1_-_The_Gay_Thing.mp3
These 34 bytes : Now: _Rollins_-_02_-_Think_Tank_-_Disc_2_-_Brazil.mp3
Are up for sale : Fwd: -_04_-_The_Boxed_Life_-_Disc_2_-_Good_Advice.mp3

Faux_Pseudo

2002-09-30, 4:28 am

Johan Lindquist

2002-10-02, 1:25 pm

On mån, 30 sep 2002 at 10:53 GMT, gazing longingly at the horizon,
Faux_Pseudo <Faux_Pseudo@yahoo.comERCIAL>
felt a deep, passionate desire to let the following be known:

> find /usr /opt /lib -name *filename -print

Quotes around the *filename[*] part would be good, no?

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
8:17pm up 29 days, 20:56, 10 users, load average: 1.41, 1.60, 1.44
$ cat /dev/bollocks Registered Linux user #261729
leverage global experiences

Faux_Pseudo

2002-10-02, 2:25 pm

_.--- Johan Lindquist spoke in alt.os.linux --------._
> On mån, 30 sep 2002 at 10:53 GMT, gazing longingly at the horizon,
> Faux_Pseudo <Faux_Pseudo@yahoo.comERCIAL>
> felt a deep, passionate desire to let the following be known:
>
>> find /usr /opt /lib -name *filename -print
>
> Quotes around the *filename[*] part would be good, no?

Nope. quots will protect the * makeing a \* and not a .*
and the [*] is a bad idea too. You would be better off with
find $PATHS -name *filename*? -print
if you are going to optionize the final *

Remebmer that find uses shell wildcards and not regex so things
behaive differently than one might expect in some cases. Which is why
I normally go with

find $PATHS -print | grep filename

So that this way I can use full regexs if I want to.

'---...____ Faux_Pseudo ________________...---~~~

--
ICQ=66618055 : --(-<= Now Playing =>-)-- http://asciipr0n.com/fp
YIM=faux_pseudo : Rev: /black_flag/in_my_head/Black_Flag-White_Hot.mp3
I am denial guilt: Now: _-_Badmotorfinger_-_03_-_Slaves_&_Bulldozers.mp3
and fear : Fwd: /black_flag/Black_Flag_-_09_-_Depression.mp3

Johan Lindquist

2002-10-02, 3:25 pm

On ons, 02 okt 2002 at 20:45 GMT, gazing longingly at the horizon,
Faux_Pseudo <Faux_Pseudo@yahoo.comERCIAL>
felt a deep, passionate desire to let the following be known:
> _.--- Johan Lindquist spoke in alt.os.linux --------._
>> On mån, 30 sep 2002 at 10:53 GMT, gazing longingly at the horizon,
>> Faux_Pseudo <Faux_Pseudo@yahoo.comERCIAL>
>> felt a deep, passionate desire to let the following be known:
[colo
r=darkred]
>>> find /usr /opt /lib -name *filename -print
>>
>> Quotes around the *filename[*] part would be good, no?
>
> Nope. quots will protect the * makeing a \* and not a .*[/color]

I was pretty certain that doing it your way would expand the *filename
in the current dir? This would pretty much make the search an
indeterminate process depending on where you execute it.

> and the [*] is a bad idea too.

It was for illustration purposes since you hinted at putting an
optional asterisk after the filename. Never mind.

> Remebmer that find uses shell wildcards and not regex so things
> behaive differently than one might expect in some cases.

I must admit I'm kinda confused now. I'm fairly certain I have had
trouble in the past using wildcards without quoting them with both
find and locate. Isn't the shell actually supposed to expand wildcards
before executing the command? Otherwise a simple thing like 'ls
foo/bar*' shouldn't even work.. right?

Perhaps it varies from shell to shell? Let's try that:

-----8<-----
licia(3)> find Mail -name sen* -print
find: No match.
licia(4)> find Mail -name "sen*" -print
Mail/sent
licia(5)> echo $SHELL
/bin/tcsh
licia(6)> /bin/bash
bash-2.03$ find Mail -name sen* -print
Mail/sent
----->8-----

That explains why I'm confused, but it doesn't help me much.

Why does bash handle wildcards differently when it comes to ls and find?

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
9:15pm up 29 days, 21:55, 9 users, load average: 1.22, 1.62, 1.89
$ cat /dev/bollocks Registered Linux user #261729
disintermediate vertical convergence

Faux_Pseudo

2002-10-02, 5:25 pm

_.--- Johan Lindquist spoke in alt.os.linux --------._
>
>>>> find /usr /opt /lib -name *filename -print
>>>
>>> Quotes around the *filename[*] part would be good, no?
>>
>> Nope. quots will protect the * makeing a \* and not a .*
>
> I was pretty certain that doing it your way would expand the *filename
> in the current dir? This would pretty much make the search an
> indeterminate process depending on where you execute it.

Every example was tested before I posted it. The reason for putting
the "/usr /opt /lib" bit in there is so that it doesn't matter where
you execute it.

>
>> and the [*] is a bad idea too.
>
> It was for illustration purposes since you hinted at putting an
> optional asterisk after the filename. Never mind.

Oh. Ok. Wild cards in regex's for the purpose of illustration doesn't
read so well. But we can't win them all.

> I must admit I'm kinda confused now. I'm fairly certain I have had
> trouble in the past using wildcards without quoting them with both
> find and locate. Isn't the shell actually supposed to expand wildcards
> before executing the command?

<snip of good tcsh bash example>

> That explains why I'm confused, but it doesn't help me much.

>
> Why does bash handle wildcards differently when it comes to ls and find?

I don't know. You might ask a [t]csh user on that one as they tend to
know more about that kind of thing. I am curious as to which is the
"correct" way however.

'---...____ Faux_Pseudo ________________...---~~~

--
ICQ=66618055 : --(-<= Now Playing =>-)-- http://asciipr0n.com/fp
YIM=faux_pseudo : Rev: /soundgarden/superunknown/Jesus_Christ_Pose.mp3
I gave you my : Now: /black_flag/Black_Flag_-_15_-_Damaged_I.mp3
purity : Fwd: /soundgarden/10_-_Uncovered.mp3

Johan Lindquist

2002-10-03, 2:25 am

On ons, 02 okt 2002 at 23:35 GMT, gazing longingly at the horizon,
Faux_Pseudo <Faux_Pseudo@yahoo.comERCIAL>
felt a deep, passionate desire to let the following be known:
> _.--- Johan Lindquist spoke in alt.os.linux --------._
[colo
r=darkred]
>>>>> find /usr /opt /lib -name *filename -print
>>>>
>>>> Quotes around the *filename[*] part would be good, no?
>>>
>>> Nope. quots will protect the * makeing a \* and not a .*
>>
>> I was pretty certain that doing it your way would expand the
>> *filename in the current dir? This would pretty much make the
>> search an indeterminate process depending on where you execute it.
>
> Every example was tested before I posted it. The reason for putting
> the "/usr /opt /lib" bit in there is so that it doesn't matter where
> you execute it.[/color]

That wasn't the point, what I meant was that if the wildcard is
expanded in whatever directory you are currently in, the search terms
will depend on where you execute the command.

Since the command still works with (double) quotes around the search
term in both bash and ksh, not knowing which shell someone is using,
it might be a Good Thing(tm) to include them when posting an example.
In the rare event that /anyone/ is still using something like csh,
that is..

>> Why does bash handle wildcards differently when it comes to ls and
>> find?
>
> I don't know. You might ask a [t]csh user on that one as they tend
> to know more about that kind of thing. I am curious as to which is
> the "correct" way however.

Well, since I "grew up" on tsch, I suppose I should know, but I don't.

Since bash, or rather sh, is older (at least I think it is?) I guess
[t]csh is the exception. *shrugs*

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
9:13am up 30 days, 9:52, 10 users, load average: 1.16, 1.08, 1.08
$ cat /dev/bollocks Registered Linux user #261729
envisioneer viral initiatives

Peter T. Breuer

2002-10-03, 5:25 am

Johan Lindquist <spam@smilfinken.net> wrote:
> Since bash, or rather sh, is older (at least I think it is?) I guess
> [t]csh is the exception. *shrugs*

No, wildcards are always expanded by the shell. You are correct. (I use
tcsh).

Peter

Sponsored Links