sed broken?

2002-06-24 Thread Motoyuki Konno

Hi,

I found that ports/devel/libtool and ports/devel/gmake are broken
on today's FreeBSD-current.  I attached the error log to this mail.
It seems that these problems caused by the recent changes (on Jul 21)
to /usr/bin/sed.

I tried to build ports/devel/libtool using old /usr/binsed
(before Jul 21),  everything goes well.

--

Motoyuki Konno  [EMAIL PROTECTED] (Home)
[EMAIL PROTECTED]  (FreeBSD Project)
http://www.freebsd.org/~motoyuki/ (WWW)


===  Extracting for libtool-1.3.4_4
 Checksum OK for libtool-1.3.4.tar.gz.
===  Patching for libtool-1.3.4_4
===  Applying FreeBSD patches for libtool-1.3.4_4
===  Configuring for libtool-1.3.4_4
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel
[snip]
creating Makefile
creating config.h
===  Building for libtool-1.3.4_4
Making all in .
[snip]
CC=cc CFLAGS=-O -pipe CPPFLAGS=  LD=/usr/libexec/elf/ld LDFLAGS= LIBS=  
LN_S=ln -s NM=/usr/bin/nm -B RANLIB=ranlib  DLLTOOL= OBJDUMP= AS=  /bin/sh 
./ltconfig --cache-file=./config.cache --with-gcc --with-gnu-ld --enable-dlopen 
--srcdir=.  --output=libtool ./ltmain.sh
loading cache ./config.cache within ltconfig
checking host system type... i386-unknown-freebsdelf5.0
checking for object suffix... o
checking for executable suffix... (cached) no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc supports -c -o file.o... yes
checking if cc supports -c -o file.lo... yes
checking if cc supports -fno-rtti -fno-exceptions ... yes
checking if cc static flag -static works... -static
checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
checking whether the linker (/usr/libexec/elf/ld) supports shared libraries... yes
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/libexec/elf/ld option to reload object files... -r
checking dynamic linker characteristics... freebsdelf5.0 ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for objdir... .libs
checking for dlopen in -ldl... (cached) no
checking for dlopen... (cached) yes
checking for dlfcn.h... (cached) yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
creating libtool
updating cache ./config.cache
CONFIG_FILES=libtoolize CONFIG_HEADERS= ./config.status
creating libtoolize
chmod +x libtoolize
Making all in libltdl
/bin/sh ./libtool --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I. -O -pipe -c ltdl.c
mkdir .libs
cc -DHAVE_CONFIG_H -I. -I. -I. -O -pipe -c ltdl.c  -fPIC -DPIC -o .libs/ltdl.lo
ltdl.c: In function `sys_dl_open':
ltdl.c:266: warning: assignment makes pointer from integer without a cast
ltdl.c:269: warning: assignment makes pointer from integer without a cast
ltdl.c: In function `sys_dl_close':
ltdl.c:284: warning: assignment makes pointer from integer without a cast
ltdl.c: In function `sys_dl_sym':
ltdl.c:298: warning: initialization makes pointer from integer without a cast
ltdl.c:302: warning: assignment makes pointer from integer without a cast
ltdl.c: In function `find_file':
ltdl.c:1085: `FILE' undeclared (first use in this function)
ltdl.c:1085: (Each undeclared identifier is reported only once
ltdl.c:1085: for each function it appears in.)
ltdl.c:1085: `file' undeclared (first use in this function)
ltdl.c: In function `lt_dlopen':
ltdl.c:1223: `FILE' undeclared (first use in this function)
ltdl.c:1223: `file' undeclared (first use in this function)
ltdl.c:1255: syntax error before ')' token
ltdl.c:1259: syntax error before ')' token
ltdl.c:1264: syntax error before ')' token
*** Error code 1

Stop in /local/ports/devel/libtool/work/libtool-1.3.4/libltdl.
*** Error code 1

Stop in /local/ports/devel/libtool/work/libtool-1.3.4.
*** Error code 1

Stop in /local/ports/devel/libtool.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: sed broken?

2002-06-24 Thread Tim Robbins

On Mon, Jun 24, 2002 at 07:09:45PM +0900, Motoyuki Konno wrote:

 Hi,
 
 I found that ports/devel/libtool and ports/devel/gmake are broken
 on today's FreeBSD-current.  I attached the error log to this mail.
 It seems that these problems caused by the recent changes (on Jul 21)
 to /usr/bin/sed.
 
 I tried to build ports/devel/libtool using old /usr/binsed
 (before Jul 21),  everything goes well.

Thanks for reporting this. I found an off-by-one error I introduced by
removing the trailing newline from the pattern space in the `y'
(transliterate) command. The last character of the pattern space was
never modified, because the code wrongly assumed a newline was there.

Here's an example of the broken behaviour:
$ echo  | sed 'y/o/O/'
OOOo

Good behaviour w/ fixed sed:
$ echo '' | sed 'y/o/O/'  


After applying the patch I'm about to commit, libtool 1.4d compiles fine.


Tim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message