>> How do you know it's supposed to be glib20 and not _glib20? I don't, but what I DO know is that after the 2 corrections (star1 and 2 from post #2), the error messages in the form of 'Unknown component _glib20' cleared out and the dependent ports got built by poudriere. So that was Makefile related. If not, suggest how it is to be fixed so that the error no longer occurs.
>> Evenmore you haven't shown anything that would point to a problem in >> poudriere itself. a. First item in post #1? I asked if there is a way to get libsamplerate in poudriere b. My thread is not limited to problems with 2 ports, since there are a good number of problems which I am posting as fast as much as I can gather the details. c. As posted in #2: colord-0.1.20_1, libsoup-2.42.0, wxgtk2-common-2.8.12 get built on host but not in poudriere. As shown, the errors are trivial (like 'cannot find sqlite3' when the sqlite3.txz is in fact located in the repo) and furthermore, packages built manually and placed in the common repo are summarily deleted by poudriere at repo-check stage. What more does one need before referring to all of this as "sillieness"? I do not know where the source problem lies exactly, so I am reporting my findings. ----- 10-Current-amd64-portstree merged with marcuscom.gnome3 & xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/poudriere-sillieness-re-audio-libsamplerate-glib20-tp5802508p5802546.html Sent from the freebsd-ports mailing list archive at Nabble.com. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"