First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 111353
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo's Team for Core System packages <base-system@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Erik MÃ¥nsson <goodbyte100@yahoo.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 111353 depends on: Show dependency tree
Show dependency graph
Bug 111353 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-11-03 05:17 0000
I have a cross platform project that I am testing on both a
"Linux ike 2.6.12-nitro5 #4 SMP Sat Sep 10 12:47:01 CEST 2005 i686 Intel(R)
"Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
and a
"SunOS login-9 5.8 Generic_117350-06 sun4u sparc SUNW,Ultra-5_10". I do the main
development on the linux box and every once in a while I make a package and test
it on the SunOS box. My problem is that the libtool version that is shipped with
gentoo (1.5.20) includes a "sanity check" to ensure ltmain.sh and libtool.m4
have same version number. The version number is extracted from ltmain.sh with:
grep '^[[:space:]]*VERSION=' ltmain.sh | sed -e 's|^[[:space:]]*VERSION=||'
but the sed version on the solaris box does not support [:space:] as a character
class and thus I get following error message:

*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.20, ltmain.sh = VERSION=1.5.20) ***

by instead using 
grep '^[[:space:]]*VERSION=' ltmain.sh | sed -e 's|^[ ]*VERSION=||'
the problem is solved.

------- Comment #1 From SpanKY 2005-11-03 05:45:21 0000 -------
i dont think we can use any character classes, be it with grep or sed

if we just rewrite it and put in the space/tab ourselves it should be
fine i think

------- Comment #2 From SpanKY 2005-11-03 18:33:26 0000 -------
fixed in 1.5.20-r1, thanks for reporting :)

First Last Prev Next    No search results available      Search page      Enter new bug