From: <w9ya@arrl.net>
To: linux-hams@vger.kernel.org
Subject: Re: hamlib not compiling well
Date: Wed, 7 Jul 2004 11:39:12 -0500 (EST) [thread overview]
Message-ID: <4900.192.168.1.117.1089218352.squirrel@gateway> (raw)
In-Reply-To: <1223.192.168.1.117.1089178842.squirrel@gateway>
Hey again gang;
I added this to the top of the spec file to get libtool to NOT libtoolize:
%define __libtoolize /bin/true
Apparently there is a libtool version mismatch somewhere ? (Just a guess.)
Mandrake uses this:
libtool-1.4.3-10mdk
Anyways, I am not sure these files actually work (grin)....but at least
they exist correctly and in the right places.
I tested this fix with the spec file that came with hamlib 1.2.0.src.rpm
btw, although this problem existed also with 1.1.4 as well.
Vy 73;
Bob
w9ya
> Hey gang;
>
> I am trying to write some Mandrake spec files for tlf and a few other
> packages. In the process I am not able to use rpm -ba to compile the
> spec files for hamlib.
>
> 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.
>
> I am sure I am just brain farting on why this is happening or much more
> importantly what it is I need to do to get a decent compile; but does
> anyone have any helpful ideas ?
>
> TIA
>
> Vy 73;
>
> Bob
> w9ya
prev parent reply other threads:[~2004-07-07 16:39 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
2004-07-07 16:39 ` w9ya [this message]
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=4900.192.168.1.117.1089218352.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