From: <w9ya@arrl.net>
To: linux-hams@vger.kernel.org
Subject: Re: hamlib not compiling well
Date: Thu, 8 Jul 2004 02:43:19 -0500 (EST) [thread overview]
Message-ID: <3626.192.168.1.117.1089272599.squirrel@gateway> (raw)
In-Reply-To: <200407080811.05522.pa3gcu@zeelandnet.nl>
> On Wednesday 07 July 2004 17:59, w9ya@arrl.net wrote:
>> >> I am running into a problem that I have not seen before. There are
>> files being created but they are without the ".so"in the file name,
>> I tried adding "--enable-shared" to the configure, but this did not
>> work, nor have I ever required this.
>> >
>> > After installing libs one needs to use 'ldconfig' to configure
>> dynamic linker run time bindings, as show in the manual page of
>> ldconfig. I presume this is your problem.
>>
>> Um, perhaps I was not clear about this. If that is my fault, I am
>> sorry.
>>
>> This is prior to installing the libs.
>
> Whatever, but i have just retrived hamlib-1.1.4.tar.bz2 decompressed it
> and simply did;
>
> ./configure
> make
> make install
>
> Things look ok to me. .so files do get created in subdirs, make install
> installs everything in /usr/local/lib and seeminly links things as well.
Hey Richard;
And well they might seem o.k. for you.
I was making rpms for Mandrake, which entails a different approach.
1 - /usr/local is off limits.
2 - File permissions and ownership issues may be present.
3 - Extraneous files may have to noticed and removed.
4 - ALL files must be accounted for.
5 - Various other distribution specific issues in many other areas often
need to be attended to. (And these can be many.)
But I definitely can say this; even with your approach, if you had tried
to do a simple compile on a Mandrake 10.0 Official machine you would have
run into the same problems I had.
BTW I reported the fix yesterday or the day before for this, so the
problem is solved; it appears to be a versioning issue with
libtool/libtldl.
Finally IMHO it is a really bad idea to just compile, even into
/usr/local, on a system (like mandrake, debian, red hat, suse, and many
other "distros") that uses a file tracking package management system. You
run the risk of system instability or worse.
Thanks for the concerns es vy 73;
Bob
w9ya
>
>> Bob
>> w9ya
>
> --
> If the Linux community is a bunch of thieves because they
> try to imitate windows programs, then the Windows community
> is built on organized crime.
>
> Regards Richard
> pa3gcu@zeelandnet.nl
> http://people.zeelandnet.nl/pa3gcu/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-07-08 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 5:40 hamlib not compiling well w9ya
2004-07-07 15:10 ` pa3gcu
2004-07-07 15:59 ` w9ya
2004-07-07 17:58 ` Just installed RedHat 9 John Montanez
2004-07-08 21:15 ` pa3gcu
2004-07-08 21:36 ` John Montanez
2004-07-09 5:39 ` John Bennett
2004-07-13 15:33 ` John Montanez
2004-07-09 21:23 ` M Taylor
2004-08-04 2:53 ` Wilbert Knol
2004-08-04 3:12 ` Jeff Camp
2004-07-08 6:11 ` hamlib not compiling well pa3gcu
2004-07-08 7:43 ` w9ya [this message]
2004-07-07 16:39 ` w9ya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3626.192.168.1.117.1089272599.squirrel@gateway \
--to=w9ya@arrl.net \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox