Re: [sr #108201] libtool problems with -export-symbols-regex on solaris with gcc-4.7.x

[Bob Friesenhahn]

On Tue, 11 Dec 2012, Dennis Clarke wrote:


Follow-up Comment #2, sr #108201 (project libtool):

I notice that the error message mentions the program name 'sed' rather
than
'gsed'.  Perhaps two different sed programs are being used?  It seems
likely
that the 'sed' which failed is Solaris 'sed' rather than GNU 'sed'.



Is there a valid reason why a POSIX compliant ( POSIX.2, POSIX.2a, SUS, SUSv2, 
XPG4  ) sed can not be used ?


This is (i.e. should be) intended to work.  However, what we seem to 
be seeing is that the sed intentionally selected for use ('gsed') was 
not always consistently used.  In a few cases bare 'sed' was used from 
Richard's PATH (which does not include /usr/xpg4/bin) and this 'sed' 
failed.


It seems that Richard started down one path (-export-symbols-regex did 
not work as expected) but now he is on a new path (sed failure).


There are several Solaris-related patches which were posted to the 
libtool list which have not yet been applied.  The libtool project is 
considerably behind at evaluating and applying patches.  I don't think 
that any of the patches are for -export-symbols-regex or sed though.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/

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

Re: [sr #108201] libtool problems with -export-symbols-regex on solaris with gcc-4.7.x

[Dennis Clarke]

- Original Message -
From: Bob Friesenhahn 
Date: Tuesday, December 11, 2012 9:57 am
Subject: [sr #108201] libtool problems with -export-symbols-regex on solaris 
with gcc-4.7.x
To: Richard PALO , Bob Friesenhahn 
, libtool@gnu.org


> Follow-up Comment #2, sr #108201 (project libtool):
> 
> I notice that the error message mentions the program name 'sed' rather 
> than
> 'gsed'.  Perhaps two different sed programs are being used?  It seems 
> likely
> that the 'sed' which failed is Solaris 'sed' rather than GNU 'sed'.
> 

Is there a valid reason why a POSIX compliant ( POSIX.2, POSIX.2a, SUS, SUSv2, 
XPG4  ) sed can not be used ? 

That would be the sed in /usr/xpg4/bin on Solaris 10 and if GNU extensions are 
required, which are not covered in the standard, the the questions is .. why?

Dennis 

ps: I know this is slightly out of scope but a continual source of problems in 
the POSIX world

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

[sr #108201] libtool problems with -export-symbols-regex on solaris with gcc-4.7.x

[Richard PALO]

Follow-up Comment #4, sr #108201 (project libtool):

I was working off of master. With git blame I noticed that the strcmp problem
was introduced recently, so I'm trying over after git checkout v2.4.2, which
is the latest tarball version I've tested with pkgsrc.

HEAD is now at fdb4c54... Release 2.4.2

hopefully it'll go a bit cleaner.

___

Reply to this item at:

  

___
  Message posté via/par Savannah
  http://savannah.gnu.org/


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

[sr #108201] libtool problems with -export-symbols-regex on solaris with gcc-4.7.x

[Richard PALO]

Follow-up Comment #3, sr #108201 (project libtool):

Hello Bob,

I wonder too, which is why I indicated at the end of my last comment:
> does libtool not like pkgsrc version of sed?
> 
> richard@devzone:~/src/libtool$ which sed
> /opt/pkg/gnu/bin/sed
> richard@devzone:~/src/libtool$ grep 'SED=' config.log
> ac_cv_path_SED=/opt/pkg/bin/gsed
> SED='/opt/pkg/bin/gsed'


Anyway, my PATH is:
richard@devzone:~/src/libtool$ echo $PATH
/opt/pkg/sbin:/opt/pkg/bin:/opt/pkg/gnu/bin:/opt/pkg/gcc47/bin:/usr/bin:/usr/sbin:/sbin

so it has to use RPN to get to Solaris 'sed'... 

shouldn't all scripts be using more or less the same 'sed' anyway?  


I'm a bit surprised after taking a look at 'egrep "sed|SED" *.mk'

After looking a bit at config.log and config.status, I'm uneasy about respect
for my PATH. 

Is there a way to get this to work on OI_151a7?  

For what it is worth, I'm able to continue with pkgsrc after manually patching
/opt/pkg/bin/libtool:

richard@devzone:~$ libtool --version
ltmain.sh (GNU libtool) 2.2.6b
Written by Gordon Matzigkeit , 1996

Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
richard@devzone:~$ pkgdiff /opt/pkg/bin/libtool
$NetBSD$

--- /opt/pkg/bin/libtool.orig   2012-12-11 12:43:45.0 +
+++ /opt/pkg/bin/libtool
@@ -8967,7 +8967,7 @@ old_archive_from_expsyms_cmds=""
 # Commands used to build a shared archive.
 archive_cmds="$CC -shared -nostdlib $LDFLAGS $predep_objects $libobjs
$deplibs $postdep_objects $compiler_flags ${wl}-h $wl$soname -o $lib"
 archive_expsym_cmds="echo \"{ global:\" > $lib.exp~cat $export_symbols | $SED
-e \"s/\\(.*\\)/\\1;/\" >> $lib.exp~echo \"local: *; };\" >> $lib.exp~
- $CC -shared -nostdlib ${wl}-M $wl$lib.exp -o $lib
$predep_objects $libobjs $deplibs $postdep_objects $compiler_flags~$RM
$lib.exp"
+ $CC -shared -nostdlib ${wl}-M $wl$lib.exp ${wl}-h $wl$soname
-o $lib $predep_objects $libobjs $deplibs $postdep_objects $compiler_flags~$RM
$lib.exp"
 
 # Commands used to build a loadable module if different from building
 # a shared archive.


It's a very short term remedy but hopefully we can rapidly get libtool, and
then pkgsrc updated.

___

Reply to this item at:

  

___
  Message posté via/par Savannah
  http://savannah.gnu.org/


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

[sr #108201] libtool problems with -export-symbols-regex on solaris with gcc-4.7.x

[Bob Friesenhahn]

Follow-up Comment #2, sr #108201 (project libtool):

I notice that the error message mentions the program name 'sed' rather than
'gsed'.  Perhaps two different sed programs are being used?  It seems likely
that the 'sed' which failed is Solaris 'sed' rather than GNU 'sed'.

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


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

[sr #108201] libtool problems with -export-symbols-regex on solaris with gcc-4.7.x

[Richard PALO]

Follow-up Comment #1, sr #108201 (project libtool):

trying to bootstrap git base to provide a test case and patch proposal, but I
notice some problems already in doing after ./bootstrap && ./configure
 
gmake check syntax-check distcheck


## - ##
## Test results. ##
## - ##

151 tests behaved as expected.
17 tests were skipped.
gmake[3]: Leaving directory `/home/richard/src/libtool'
gmake[2]: Leaving directory `/home/richard/src/libtool'
gmake[1]: Leaving directory `/home/richard/src/libtool'
GFDL_version
0.12 GFDL_version
...
libtool_m4_cc_basename
sed: -e expression #1, char 86: unterminated address regex
0.03 libtool_m4_cc_basename
...
prohibit_set_dummy_without_shift
sed: -e expression #1, char 136: unterminated address regex
0.08 prohibit_set_dummy_without_shift
...
prohibit_strcmp
build-aux/ltmain.in:2824:   $SED 's/.*/  if (!strcmp
(symbol->name, "&")) symbol->address = (void *) &&;/' < "$nlist"I >>
"$output_objdir/$my_dlsyms"
maint.mk: replace strcmp calls above with STREQ/STRNEQ
gmake: *** [sc_prohibit_strcmp] Error 1

does libtool not like pkgsrc version of sed?

richard@devzone:~/src/libtool$ which sed
/opt/pkg/gnu/bin/sed
richard@devzone:~/src/libtool$ grep 'SED=' config.log
ac_cv_path_SED=/opt/pkg/bin/gsed
SED='/opt/pkg/bin/gsed'



___

Reply to this item at:

  

___
  Message posté via/par Savannah
  http://savannah.gnu.org/


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