「激写!投稿白書!〜100％素人のみ〜」です。

[[EMAIL PROTECTED]]

$B!V7chttp://e-excite.jp

$B$*5RMM$OEv%5%$%H$NM-NA%3!<%J!<$4MxMQF|$h$j#3F|0J>e7P2a$7$^$7$?$,MxMQNA6b!!(B
$B#2#8#0#0#01_$,L$G<$H$J$C$F$*$j$^$9!#;j5^2<5-8}:B$X$*?69~2<$5$$!#(B
[EMAIL PROTECTED]|[EMAIL PROTECTED]>l9g$^$?$O$4O"[EMAIL 
PROTECTED]>l9g$O!VDL>o(B
$BNA6b!W$N#6K|[EMAIL PROTECTED];[EMAIL 
PROTECTED]/$3$H$K$J$j$^$9!#$4N;>5$/[EMAIL PROTECTED](B
$B$3$N$^$^J|CV$5$l$^$9$H$*5RMM$N%G!<%?$r2s<}It$X0\4I$7$^$9$N$G$4N;>52<$5$$!#(B
$B"([EMAIL PROTECTED];[EMAIL PROTECTED]@A5a$G$"[EMAIL PROTECTED]"$j$^$;$s!#(B

$B"(:G6a$*L>A0$G$N$*?69~$,L\$KIU$-$^$9!#(B
$B$*L>A0$G$N4IM}$O$7$F$*$j$^$;$s$N$GF~6b:Q$_$K=PMh$^$;$s$N$G(B
$B$*L>A0$G$*?69~$NJ}$O%a!<%k$K$F$*CN$i$;$/[EMAIL PROTECTED](B

$B"(EvJ}$N%7%9%F%`$NET9g>[EMAIL PROTECTED](B
$B$3$N%a!<%k$,Ce$/>l9g$,$"$j$^$9$,$=$N>l9g$O(B
[EMAIL PROTECTED];$s$N$G$4N;>5$/[EMAIL PROTECTED](B
$B"(Ev%5%$%H$G$O!"!VEE;R>CHq<[EMAIL PROTECTED]/NA6bI=<(5Z$S?=$79~$_%\%?%s!W(B 
$B$N(B
[EMAIL PROTECTED](B : $B%/%K%^%D%^%5%-(B

$B"#?69~?ML>5A(B

$B$*5RMM$N!V?69~#I#DHV9f!W$G$*4j$$$7$^$9!#(B
$B!V?69~#I#DHV9f!W$,J,$+$i$J$$>l9g$O!V$*L>A0!W$G$*?69~$_D:$$$F$b7k9=$G$9!#(B
[EMAIL PROTECTED]"$=$N:]$O?69~$_$N:]$N!V$*L>A0!W$r;vL36I$^$G$*CN$i$;$/[EMAIL 
PROTECTED](B


$B"#$*Ld9g$;@h(B

$B%"%I%3%`4k2h!!(B
[EMAIL PROTECTED]



___
http://lists.gnu.org/mailman/listinfo/libtool

Portland compiler support

[Jeff Squyres]

I have recently discovered that the Portland support that I sent 
patches in for does not work for shared libraries (a LAM/MPI user told 
me this -- not the Portland support group, which I find odd).

HINT: PGI -- I'd really like to hear from you; I heard nothing from you 
last time, which ended up in incorrect support for PGI compilers in 
Libtool.  Let's not get this wrong again and cause confusion for your 
customers...

The issue is that when making shared libraries with --whole-archive, 
the PGI linker needs one big argument 
("-Wl,--whole-archive,foo.a,bar.a,baz.a") as opposed to a 
space-sparated list ("-Wl,--whole-archive foo.a bar.a baz.a").

I'm trolling through the source code to figure out how to do this -- I 
see that $convenience is built up as a space separated list.  I'm 
trying to figure out the exact flow of things, but my first 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!)

--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/

___
http://lists.gnu.org/mailman/listinfo/libtool

Buy me a Role.x

[Tyrone Toney]

R0LEX watches at extremely low prices.. only a few crates left so if you want one hurry
Grab yours here - 10 styles to pick from
 


___
http://lists.gnu.org/mailman/listinfo/libtool

Re: Portland compiler support

[Peter O'Gorman]

Jeff Squyres wrote:
I have recently discovered that the Portland support that I sent patches 
in for does not work for shared libraries (a LAM/MPI user told me this 
-- not the Portland support group, which I find odd).

The issue is that when making shared libraries with --whole-archive, the 
PGI linker needs one big argument 
("-Wl,--whole-archive,foo.a,bar.a,baz.a") as opposed to a space-sparated 
list ("-Wl,--whole-archive foo.a bar.a baz.a").

I'm trolling through the source code to figure out how to do this -- I 
see that $convenience is built up as a space separated list.  I'm trying 
to figure out the exact flow of things, but my first impression is that 
it might be easiest to just parameterize on the delimiter (" " or ",") 
in $convenience.  Am I off base here?
Hi Jeff,
In a case such as this it would probably be best to set
whole_archive_flag_spec to the empty string. This will cause libtool to
unpack the static archive and add the objects to the link line. I'll look
and send you a patch to try tonight (JST).
Peter
--
Peter O'Gorman - http://www.pogma.com
___
http://lists.gnu.org/mailman/listinfo/libtool

Still no joy....

[Bruce Korb]

I have now changed the Makefile.am thus:

  autogen_LDADD = $(top_builddir)/autoopts/libopts.la $(LIBGUILE_LIBS)

and autogen_LDFLAGS = -export-dynamic.  The net result:

> + /home/bkorb/ag/ag/agen5/autogen \
> -L/home/bkorb/ag/ag/autoopts argument.def
> /home/bkorb/ag/ag/agen5/.libs/lt-autogen: symbol lookup error: \
> /home/bkorb/ag/ag/agen5/.libs/lt-autogen: undefined symbol: optionStackArg
> + failure AutoGen could not process
> 
> $ nm /home/bkorb/ag/ag/autoopts/.libs/libopts.so|fgrep optionStackArg
> bb31 T optionStackArg

It is not finding the symbol because it is not looking in
the current build directory.  So, I guess I have a bug.
Attached is the script /home/bkorb/ag/ag/agen5/autogen.
I think what is needed should be clear from the above,
but I'll be happy to send any more information that might
be helpful!

Thank you - Bruce


autogen
Description: application/shellscript
___
http://lists.gnu.org/mailman/listinfo/libtool