On 12/20/2010 08:02 PM, Bruce Korb wrote:
On 12/20/10 09:11, Nick Bowler wrote:
On 2010-12-20 08:54 -0800, Bruce Korb wrote:
If the default build is 64 bit, why does it make sense that the
default library directory is the 32 bit library?
As far as I know, the only reason for this design is to
* Bruce Korb wrote on Mon, Dec 20, 2010 at 09:37:58PM CET:
> On 12/20/10 11:20, Ralf Wildenhues wrote:
> > One crucial part is that libtool gets confused whenever it has
> > directories with the wrong ABI in the search path (unlike ld or ld.so,
> > both are in some cases smart enough to skip wrong
On 12/20/10 11:20, Ralf Wildenhues wrote:
> * Bruce Korb wrote on Mon, Dec 20, 2010 at 03:09:48PM CET:
>> How much understanding of the machinery should be expected
>> of the hapless project builder?
>
> I've skimmed most of the conversation in this thread now.
>
> The crucial part, I think,
* Ralf Wildenhues wrote on Mon, Dec 20, 2010 at 08:20:25PM CET:
> The other crucial part is that libtool doesn't get the
> sys_lib_search_path_spec and sys_lib_dlsearch_path_spec settings
> right on several distros, introducing such wrong directories itself (not
> to speak of cross setups). There
* Bruce Korb wrote on Mon, Dec 20, 2010 at 03:09:48PM CET:
> How much understanding of the machinery should be expected
> of the hapless project builder?
I've skimmed most of the conversation in this thread now.
The crucial part, I think, is *not* the --libdir setting. Distros
usually get th
On 12/20/10 09:11, Nick Bowler wrote:
> On 2010-12-20 08:54 -0800, Bruce Korb wrote:
>> If the default build is 64 bit, why does it make sense that the
>> default library directory is the 32 bit library?
>
> As far as I know, the only reason for this design is to avoid breaking
> 32-bit proprietar
On 12/20/2010 10:54 AM, Bruce Korb wrote:
If the default build is 64 bit, why does it make sense that the
default library directory is the 32 bit library?
Because the user may not be building for multiple architectures, in
which case a default of $prefix/lib for libdir makes perfect sense an
On 2010-12-20 08:54 -0800, Bruce Korb wrote:
> If the default build is 64 bit, why does it make sense that the
> default library directory is the 32 bit library?
As far as I know, the only reason for this design is to avoid breaking
32-bit proprietary software with /usr/lib paths hardcoded into th
Howdy,
It is feeling like circular responsibilities to me.
So far, the circle seems unbroken. Let's start by
enumerating the ways of breaking it and then, perhaps,
figure out the easiest way. Currently, it is actually
broken by users having to know that for a particular
distribution, they have t
On 12/20/2010 04:41 PM, Eric Blake wrote:
On 12/20/2010 08:36 AM, Ralf Corsepius wrote:
If a distro insists on shipping 64-bit libraries under /usr/lib64, then
it would be in the distro's best interest to also ship a config.site
variable that defaults --libdir to the appropriate /usr/lib64 locat
On 12/20/2010 08:36 AM, Ralf Corsepius wrote:
>> If a distro insists on shipping 64-bit libraries under /usr/lib64, then
>> it would be in the distro's best interest to also ship a config.site
>> variable that defaults --libdir to the appropriate /usr/lib64 location.
>
> This isn't of much help on
On 12/20/2010 04:05 PM, Eric Blake wrote:
On 12/20/2010 07:59 AM, Bruce Korb wrote:
Hi Andy, Ralf, et al.,
On Mon, Dec 20, 2010 at 6:23 AM, Andy Wingo wrote:
How much understanding of the machinery should be expected
of the hapless project builder?
I'm not sure, but: .
I am sure
On 12/20/2010 03:59 PM, Bruce Korb wrote:
Hi Andy, Ralf, et al.,
(With my Fedora Packaging Committee member hat on) In Fedora
and RHEL, users are supposed to pass
--libdir=/usr/lib64 to configure
on x86_64 and
It is unclear that you-all can do otherwise, without having OSX-style
mixed word si
On 12/20/2010 07:59 AM, Bruce Korb wrote:
> Hi Andy, Ralf, et al.,
>
> On Mon, Dec 20, 2010 at 6:23 AM, Andy Wingo wrote:
>>> How much understanding of the machinery should be expected
>>> of the hapless project builder?
>>
>> I'm not sure, but: .
>
> I am sure of this: It needs to be m
Hi Andy, Ralf, et al.,
On Mon, Dec 20, 2010 at 6:23 AM, Andy Wingo wrote:
>> How much understanding of the machinery should be expected
>> of the hapless project builder?
>
> I'm not sure, but: .
I am sure of this: It needs to be minimized. If there are insurmountable
problems in figur
On 12/20/2010 03:09 PM, Bruce Korb wrote:
On 12/19/10 20:40, Noah Lavine wrote:
Hello,
I am not at all an expert on guile-config, but I will help if I can.
Thank you to all who responded.
Usually if you have 64-bit libs in lib64, you have to pass --libdir
explicitly.
We've now concluded t
Hi Bruce,
Sorry you and others have had to suffer through this.
On Mon 20 Dec 2010 15:09, Bruce Korb writes:
> How much understanding of the machinery should be expected
> of the hapless project builder?
I'm not sure, but:
> Nelson has been doing this stuff for quite a while and has
> rea
On 12/19/10 20:40, Noah Lavine wrote:
> Hello,
>
> I am not at all an expert on guile-config, but I will help if I can.
Thank you to all who responded.
> Usually if you have 64-bit libs in lib64, you have to pass --libdir
> explicitly.
We've now concluded that that is, indeed, the answer to the
Hello,
When a work subscription to libtool and a home subscription to
guile-devel collide...
On Mon 20 Dec 2010 05:40, Noah Lavine writes:
> I found the file that pkg-config will be using to give you this
> information. It is meta/guile-.pc in my Guile source
> tree. Furthermore, I think it's s
Hello,
I am not at all an expert on guile-config, but I will help if I can.
First of all, as to how guile-config works. At least in the latest git
version, it seems to be a thin wrapper for pkg-config.
I found the file that pkg-config will be using to give you this
information. It is meta/guile-
On 12/17/10 13:37, Peter O'Gorman wrote:
>> I haven't had a problem with setting --libdir at configure time and then
>> running make && make install, do you perhaps recall what packages gave
>> you issues with this?
>
> Oh, I misread again, just for a change :( I don't think setting libdir
> in th
On 12/17/2010 02:59 PM, Peter O'Gorman wrote:
On 12/17/2010 11:09 AM, Nelson H. F. Beebe wrote:
I normally do builds on the AMD64 platforms with something like this
(at a minimum):
env LDFLAGS='-L/usr/local/lib64 -Wl,-rpath,/usr/local/lib64' ./configure
make all check
make install libdir=/usr/
On 12/17/2010 11:09 AM, Nelson H. F. Beebe wrote:
I normally do builds on the AMD64 platforms with something like this
(at a minimum):
env LDFLAGS='-L/usr/local/lib64 -Wl,-rpath,/usr/local/lib64' ./configure
make all check
make install libdir=/usr/local/lib64
It does no
Hi Nelson,
I am nearly certain we (you) have reached a point where
libtool folks are going to say, "it is Guile", and Guile
folks are going to say, "it is libtool". I am going to
say, "I'd like some help from either or both".
Because the guile-config invokes the guile binary in order
to print ou
Hi Nelson,
On Fri, Dec 17, 2010 at 9:09 AM, Nelson H. F. Beebe wrote:
> The recent exchanges about the /usr/local/lib vs /usr/local/lib64
> problem with libtool + autogen + guile gave me a critical clue. I
> examined all of the /usr/local/lib64/*.la files, and found dozens that
> mention (incorr
The recent exchanges about the /usr/local/lib vs /usr/local/lib64
problem with libtool + autogen + guile gave me a critical clue. I
examined all of the /usr/local/lib64/*.la files, and found dozens that
mention (incorrectly) /usr/local/lib.
A couple of passes with "sed -i" scripts repaired them,
On Fri, Dec 17, 2010 at 12:14 AM, Bruce Korb wrote:
> `guile-config link` yields that string. In fact, it yields:
>
>> -L/usr/local/lib -lguile -lltdl -L/usr/local/lib64 -lgmp -lcrypt -lm -lltdl
>> -lm -ldl
>
> NOTE: " -Wl,-rpath,/usr/local/lib64 " gets inserted some how.
Well, that's broken.
On Fri, Dec 17, 2010 at 12:14:30AM -0800, Bruce Korb wrote:
> `guile-config link` yields that string. In fact, it yields:
>
> > -L/usr/local/lib -lguile -lltdl -L/usr/local/lib64 -lgmp -lcrypt -lm
> > -lltdl -lm -ldl
>
> NOTE: " -Wl,-rpath,/usr/local/lib64 " gets inserted some how.
Though rpa
`guile-config link` yields that string. In fact, it yields:
> -L/usr/local/lib -lguile -lltdl -L/usr/local/lib64 -lgmp -lcrypt -lm -lltdl
> -lm -ldl
NOTE: " -Wl,-rpath,/usr/local/lib64 " gets inserted some how.
Also, I thought the -L options were searched most recent to oldest,
but I am likel
On Thu, Dec 16, 2010 at 5:39 PM, Bruce Korb wrote:
>
> Here is the problem:
>
>> /bin/sh ../libtool --tag=CC --mode=link gcc -std=gnu99
>> -I/usr/local/include \
>> -pthread -g -O2 -export-dynamic -o autogen autogen-ag.o
>> ../autoopts/libopts.la \
>> ../snprintfv/libsnprintfv.la -pthread
Here is the problem:
> /bin/sh ../libtool --tag=CC --mode=link gcc -std=gnu99 -I/usr/local/include
> \
> -pthread -g -O2 -export-dynamic -o autogen autogen-ag.o
> ../autoopts/libopts.la \
> ../snprintfv/libsnprintfv.la -pthread \
> -L/usr/local/lib -lguile -lltdl \
> -L/usr/local/lib64
31 matches
Mail list logo
