Date: Mon, 1 Jun 1998 10:29:50 -0700 From: Josh MacDonald <jmacd@paris.CS.Berkeley.EDU> To: Paul van der Zwan <paulz@trantor.stuyts.nl> Cc: current@FreeBSD.ORG Subject: Re: Undefined symbols referenced Message-ID: <19980601102950.15326@paris.CS.Berkeley.EDU> In-Reply-To: <199805312224.AAA29878@trantor.stuyts.nl>; from Paul van der Zwan on Mon, Jun 01, 1998 at 12:24:51AM %2B0200 References: <19980531103654.23417@paris.CS.Berkeley.EDU> <199805312224.AAA29878@trantor.stuyts.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't know what your problem is. I don't have a current system to test this on. The errors indicate that xdelta can't find its read() and write() system calls, this should not happen! Jonathan Bresler has replied explaining what the possible sources of this are, and it is almost surely related to the recent changes to accomdate weak symbols and libc_r. I am unable to defend myself here without a system to test on, can someone current please help? -josh Quoting Paul van der Zwan (paulz@trantor.stuyts.nl): > > Quoting Paul van der Zwan (paulz@trantor.stuyts.nl): > > > I had the same problem a week or so ago. The xdelta port will not build on > > > current ( cvsupped and make world this weekend) even rebuilding the gdbm port > > > and reinstalling that does not work. > > > Gimp will now build because the maintainer removed the dependency on xdelta > > > but the xdelta port looks broken on current. > > > > I would say that current looks broken on xdelta. More specifically, your > > current looks broken. I don't appreciate hearing this type of report, which > > indicates the xdelta is to blame. I've gotten at least 10 of these reports. > > I don't like to hear that xdelta has been removed from GIMP either. People > > with these problems should not be running -current. > > > > -josh > > What kind of problems ?? I don't like blaming something/one for my problems, > but in this case in am just reporting a problem and in my opinion if there is > a port does not build on current, it's the port and not currrent that is broken > esp. if other ports stil build fine. > In this case it is the combination of current and the xdelta 0.18 > port that does not work.. I run current willingly and I know the problems > it can cause, but if I follow al the steps like compiling all ports another > port depends on, on an otherwise normal and up-to-date current, than that > port is broken ( for current). > Can you compile xdelta-0.18 on an up-to-date vanilla current with the system > cc ??? If so it means our systems are not entirely identical and the > difference might cause the port not to compile on my box. > If removing xdelta from the GIMP port causes GIMP to work fine , that's OK > with me, to be honest I have never noticed xdelta until it caused GMIP not to > build. > > Paul > > -- > Paul van der Zwan paulz @ trantor.stuyts.nl > "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980601102950.15326>