Date: Tue, 31 Mar 1998 09:19:41 -0800 (PST) From: asami@FreeBSD.ORG (Satoshi Asami) To: shimon@simon-shapiro.org Cc: freebsd-ports@FreeBSD.ORG, deischen@iworks.InterWorks.org Subject: Re: editor/nedit patching fails Message-ID: <199803311719.JAA17887@silvia.HIP.Berkeley.EDU> In-Reply-To: <XFMail.980331091043.shimon@simon-shapiro.org> (message from Simon Shapiro on Tue, 31 Mar 1998 09:10:43 -0800 (PST))
next in thread | previous in thread | raw e-mail | index | archive | help
* I still am at a loss as to what I am doing wrong, or how to improve myself * in this area. Most packages I build work fine. Some do not. My system is * composed of a make world of cvsupp'ed sources. So, if patch is the wrong * patch, what am I to do? Do not assume my abilities, as I am, in this * excercise trying to evaluate what skill level is necessary to build an * internal release. First, make sure that you don't have any old patches lying around. The best way is to go to ftp.freebsd.org, fetch the portball (not distfile) of the port, and run a md5 check on all files. * Ports are very uneven. I am trying to sort them out. Oh, definitely. You don't even want to hear what I have to do to build all the packages quickly on the same machine. But if you build one at a time, that shouldn't be too hard. * Nope. Not totally. I had ONE case of a corrupt package. This was * admitted and apologized for. And a bunch of "but it works for me" reports. :> * bgcc1-test -nostartfiles -nostdlib `./xgcc -B./ --print-libgcc-file-name` * cc -DCROSS_COMPILE -DIN_GCC -O -pipe -I. -I. -I./config -o g++-cross * -DGCC_ * NAME=\"`t='-e s,^,m68k-palmos-coff-,'; echo gcc | sed $t`\" ./cp/g++.c * version.o * obstack.o ` case "cc" in "cc") echo "" ;; esac ` * cc1: Invalid option `68000' * cc1: Invalid option `-Wno-multi-char-const' * *unknown*: Assembler messages: * *unknown*:0: Warning: /usr/bin/as: I don't understand 'm' flag. : No idea about this one. By the way, this part looks like this on my machine: === cp ./config/m68k/palmos_link.ld pilot.ld Testing libgcc1. Ignore linker warning messages. ./xgcc -B./ -DCROSS_COMPILE -DIN_GCC -O2 -pipe -I./include libgcc1-test.o -o li bgcc1-test -nostartfiles -nostdlib `./xgcc -B./ --print-libgcc-file-name` cc -DCROSS_COMPILE -DIN_GCC -O2 -pipe -I. -I. -I./config -o g++-cross -DGCC_ NAME=\"`t='-e s,^,m68k-palmos-coff-,'; echo gcc | sed $t`\" ./cp/g++.c version.o obstack.o ` case "cc" in "cc") echo "" ;; esac ` rm -f cxxmain.c === Hmm. This might be genuine. People with -current, please test this one. (It seems the port built fine during Justin's most recent pass (Feb 15).) * Now, shall I abandon trying to compile ports, or are ALL ports supposed to * build on any properly installed FreeBSD box (You have yet to show me where * my system is not properly installed (I'll give you a login to prove it. If * you do, I'll buy you dinner next time I am in the BA). I'd like to take you up on that offer (what's your budget? :), but don't have much time now. Please check back in a week or so. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803311719.JAA17887>