Other than Bob's humorous reply, any comment from the Libtool team?
Thanks!
--
Jeff Squyres
jsquy...@cisco.com
From: Bob Friesenhahn
Sent: Friday, March 25, 2022 4:01 PM
To: Jeff Squyres (jsquyres)
Cc: libtool@gnu.org
Subject: Re: Libtool roadma
active development? If so, is there a roadmap and/or set of
timeframes for future GNU Libtool work?
Thanks for any information that you can provide.
--
Jeff Squyres
jsquy...@cisco.com
On Sep 10, 2012, at 4:33 PM, Jeff Squyres wrote:
> I'll followup with a local edit to my valgrind suppression file and send a
> note upstream to the valgrind folks.
If anyone cares, Julian came back with a better solution within a few minutes:
https://bugs.kde.org/show_bug.cg
d even
> does computations on the tail bytes, but where the computations don't
> matter because the algorithm necessarily detects the end of string the
> the hed bytes.
Ah -- this is a much better solution.
I'll followup with a local edit to my valgrind suppression file and send a
e this supported functionality, perchance? I
would be happy to provide a patch if the idea isn't terrible.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
___
https://lists.gnu.org/mailman/listinfo/libtool
27;m a long-time/loyal LT user
and greatly appreciate all your efforts -- I'm *NOT* trying to start a
flamewar. I sent this email (and the emails back when 2.2.6a was
released) not to be a jerk, but rather to ask a genuine user-
perspective question and hopefully get some clarity f
the verbose
output of any failed test groups, and the output from `./libtool
--config.' The README file explains how to capture the verbose test
output.
--
Jeff Squyres
jsquy...@cisco.com
___
http://lists.gnu.org/mailman/listinfo/libtool
his is just
something that surprised me because it went against prior conventions,
so I thought I'd mention it on the list.
--
Jeff Squyres
Cisco Systems
___
http://lists.gnu.org/mailman/listinfo/libtool
I notice that libtool-2.2.6a.tar.* unzips into the libtool-2.2.6/
directory (dropping the "a" from the directory name). This is
unexpected. It actually throws off all my auto-install scripts
because the version number is now not the same as the directory.
Grumble.
--
Je
Disregard -- I really should have sent this to the bug-libtool list.
I'll follow up with this issue there. Sorry for the spam! :-(
On May 21, 2008, at 11:03 AM, Jeff Squyres wrote:
The Open MPI project just switched yesterday to using LT 2.2.4, AC
2.62, and AM 1.10.1 for our ni
know the history of this -fPIC -> -KPIC
change for ifort? It seems like using -fPIC for all versions of ifort
should work properly.
Thanks for all your hard work on Libtool!
--
Jeff Squyres
Cisco Systems
___
http://lists.gnu.org/mailman/listinfo/libtool
w that).
The C code could simply traverse LD_LIBRARY_PATH and look for libibverbs,
but that then subverts the ld.so mechanisms and also generally seems icky.
--
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems
___
http://lists.gnu.org/mailman/listinfo/libtool
solve our problem.
Are there any estimates of how many other applications will be hurt by this
change to libltdl? We might be among the first of many to ask about this.
:-)
--
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems
___
http://lists.gnu.org/mailman/listinfo/libtool
d to set up)?
'fraid not. We only needed C libraries to build with LAM/MPI -- the
C++ templating issue came up after that was solved. Sorry! :-(
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
cxx_find_template_repository.m4
Description: Binary data
___
http://lists.gnu.org/mailman/listinfo/libtool
h, because AM would be the one with this knowledge (i.e.,
know which source files belong to which library) -- I don't know how AM
would pass this information down to LT [in a clean manner]...
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
___
be trivial, we can just add a
command to archive_cmds/archive_expsyms_cmds/old_archive_cmds and be
done mostly.
Cheers,
Ralf
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
___
http://lists.gnu.org/mailman/listinfo/libtool
pgcc_need_extra=`expr $pgcc_major_ver \< 6`
So if $pgcc_need_extra is 1, then we need to do the multi-step
procedure listed above.
How does that sound?
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
___
http://lists.gnu.org/mailman/listinfo/libtool
I just created a toy project based with templated functions on the one
from that thread and I get similar errors. So no, it's not solved.
Do you know the right pgCC mojo to compile libraries with templates?
On Feb 24, 2005, at 9:45 AM, Markus Christen wrote:
Jeff Squyres wrote:
I have rec
On Feb 24, 2005, at 9:37 AM, Jeff Squyres wrote:
For those not following the libtool-patch list, Peter wrote up a nice
patch that seems to be working perfectly. It's been committed on
branch-1-5.
Oops! I lied -- it *hasn't* been committed yet; it's awaiting peer
review.
ks-ass.net
GNU Hacker / )= http://www.gnu.org/software/libtool
Technical Author `(_~)_ http://sources.redhat.com/autobook
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
___
http://lists.gnu.org/mailman/listinfo/libtool
For those not following the libtool-patch list, Peter wrote up a nice
patch that seems to be working perfectly. It's been committed on
branch-1-5.
On Feb 22, 2005, at 5:35 PM, Peter O'Gorman wrote:
Jeff Squyres wrote:
I have recently discovered that the Portland support that I sent
impression
is that it might be easiest to just parameterize on the delimiter (" "
or ",") in $convenience. Am I off base here?
(still trolling through the code; I am *not* a Libtool expert!
Comments / suggestions would be appreciated!)
--
{+} J
.g.:
dest-stamp: src
cp -p src dest
date >dest-stamp
I don't see any signs in it of `cp -p' being non-portable.
If this is true, then even if -p is portable, it potentially won't
solve the problem. :-\
--
{+} Jeff Squyres
{+} [
s of "touch" statements to
modify the mtime/ctime all the relevant AM-specific files in the Right
Order so that the timestamps will be proper.
2. Copy the files over in order in the first place (i.e., don't use a
glob).
3. Tar up the source directory and untar it i
MAIL PROTECTED] or
reply back with REMOVE in the SUBJECT with this email address:
libtool@gnu.org
___
http://lists.gnu.org/mailman/listinfo/libtool
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
__
applications.
So I'd say that it's probably a pretty big problem. :-\
On Feb 7, 2005, at 11:01 PM, Peter O'Gorman wrote:
-BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeff Squyres wrote:
|
| From here, I get lots of [expected] messages about missing pthread
| symbols. This is so
ditto for LT <1.5.10 that I can remember).
What happened?
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
___
http://lists.gnu.org/mailman/listinfo/libtool
branch-2-0 -- that add support for the Portland Group pgcc, pgCC, and
pgf77 compilers to Libtool. Both pass their respective test suites.
The 2-0 patch ended its test suite with:
All 115 tests passed
(no tests were skipped or failed)
Thanks!
--
{+} Je
ov 24, 2004, at 3:05 AM, Ralf Wildenhues wrote:
Hi Jeff,
* Jeff Squyres wrote on Tue, Nov 23, 2004 at 08:12:43PM CET:
I'm working on the Portland Group compilers patch for both the libtool
CVS HEAD and the 1-5 branch (both are attached), and as suggested, am
trying to run the "make check&qu
x27;s "make check"
using the GNU compilers
Both testsuite logs show the same kinds of failures.
Am I doing something wrong? (similar behavior occurs with gcc/g++/g77)
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
lt-1-5-pgi.patch
Description: Binary data
lt-h
reasonable plan. Let me port this over to the CVS
HEAD and see if it helps refine the 1.5 patch. Today's pretty hosed
for me; I can probably get to this tomorrow or over the weekend.
Many thanks.
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
[snipped]
But certainly there will be more problems with pgcc? What about pgf77
and pgCC? Could you or one of your consumers be bothered to try
branch-2-0 of libtool (1.9f will do fine as well) and report us more
possible problems its testsuite reports (VERBOSE=x output for failed
tests is
giously wrong -- if it is, any
advice on making it Right would be tremendously appreciated!
Looks good. The branch-2-0 equivalent would be similar -- just grep
for
ccc in libtool/m4/libtool.m4.
Will do.
I'll check into CC/f77 issues and post back with a new set of patches
-- for 1.5.x and 2.x.
Thanks
$1)='-Wl,'
# All Alpha code is PIC.
Please forgive me if this patch is egregiously wrong -- if it is, any
advice on making it Right would be tremendously appreciated!
Many thanks for your time.
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
___
34 matches
Mail list logo
