Two levels of pointers should not cause a problem, if he wants to go that
route. Or, he could execute a couple of commands to identify the files that
contain the unwanted path, and change them to the desired path. Just off
the top of my head (please validate before really using):
cd /to/toplevel/directory
find . -type f -exec grep -l "-L/abc/def/ghi" {} \; >filelist
for name in `cat filelist`; \
do cp $name tempfile; \
sed -e 's%-L/abc/def/ghi%-L/zyx/vvvu/tsr%' tempfile>$name; \
done;
Mark Post
-----Original Message-----
From: Davis, Jeff [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 18, 2002 9:49 AM
To: [EMAIL PROTECTED]
Subject: Linux program question
I have a user doing some programming on our SuSE Linux for S390 system. He
has the following question.
>
> The question for today is:
>
> "How carried away can I get with Linux file pointers?"
>
> Here is my problem. I have about 150 Makefiles in 150 different
> directories that have two pieces of information that need to be changed.
> Not being accustomed to the Linux or Unix world, I have no clever
> utilities to make mass changes that I'm used to in TSOland and now isn't a
> really good time to learn them as this is a quick and dirty effort to
> demonstrate that a application can be ported from Unix to Linux.
>
> The first is an include library that I need to change from -L/abc/def/ghi
> to -L/zyx/vvvu/tsr.
> Now I recognize that I could reasonably put a pointer in the /abc/def
> directory that points ghi to /zyx/wvu/tsr and all will be well.
>
> The real question is the -ltcl8.0 include in the 150 makefiles. Can I put
> a pointer in the /zyx/wvu/tsr directory named libtcl8.0 that points to
> /zyx/wvu/tsr/libtcl8.3 and get away with it or will the linker explode?
>
>
>
>
>
The information in this electronic mail message is sender's business
Confidential and may be legally privileged. It is intended solely for the
addressee(s). Access to this Internet electronic mail message by anyone
else is unauthorized. If you are not the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be taken
in reliance on it is prohibited and may be unlawful.
The sender believes that this E-mail and any attachments were free of any
virus, worm, Trojan horse, and/or malicious code when sent. This message and
its attachments could have been infected during transmission. By reading
the message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action about viruses and
other defects. Galileo International is not liable for any loss or damage
arising in any way from this message or its attachments.
