From owner-freebsd-current@freebsd.org Wed Nov 18 20:46:34 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D198CA3298E for ; Wed, 18 Nov 2015 20:46:34 +0000 (UTC) (envelope-from rizzo.unipi@gmail.com) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 56AC41127; Wed, 18 Nov 2015 20:46:34 +0000 (UTC) (envelope-from rizzo.unipi@gmail.com) Received: by lbbsy6 with SMTP id sy6so31758403lbb.2; Wed, 18 Nov 2015 12:46:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=lP4nlWK4Z1pFJtgw9xQwG+5iyEmFGmckXNQHARkCr7Q=; b=ERhkebR5JNIeOo/jdDxA9iAftvArjnq4IugoiXzfZfu3o28olJQ0yQ6t8Q1koig4Hf m5T7JCAb5lZ5PM1DurBkbPd9Iyz05lXIvOP/vK6jlHQpCKJ9iPr14AxFmX9qlzMy1fll SIOzIEBYfzIjpnf5AM+Pe9vQi8q+5Eu7NBOoHruUXqCJSc4PSlYR5IISsrMZJ6+FtLQ9 vkQYEt89g9OnXtXTnWhZ3xRusMEc/fZiiIjsAfZoD+6S7ft4qA9LVs9CEdgbnjhiYck8 xiYy02KKqA38d9bpHBMkF+q86ty9yfqTikEKLjeDIMzq19gr6AS8lWdOBHF2ba72DTyj Z7Iw== MIME-Version: 1.0 X-Received: by 10.112.136.136 with SMTP id qa8mr1657631lbb.14.1447879592227; Wed, 18 Nov 2015 12:46:32 -0800 (PST) Sender: rizzo.unipi@gmail.com Received: by 10.114.78.3 with HTTP; Wed, 18 Nov 2015 12:46:32 -0800 (PST) In-Reply-To: <20151118193252.GE27296@e-new.0x20.net> References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro> <5648C964.2020405@freebsd.org> <2DF061E9-2541-4B10-9744-C49C515FF672@gmail.com> <5648CBA1.9010300@freebsd.org> <20151118193252.GE27296@e-new.0x20.net> Date: Wed, 18 Nov 2015 12:46:32 -0800 X-Google-Sender-Auth: dON2socThVUPPFHrPuzjN68ekwA Message-ID: Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? From: Luigi Rizzo To: Lars Engels , Allan Jude , Garrett Cooper , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 20:46:34 -0000 On Wed, Nov 18, 2015 at 11:32 AM, Lars Engels wrote: > On Sun, Nov 15, 2015 at 01:14:57PM -0500, Allan Jude wrote: >> You can setup an atexit() call to call xo_finish automatically when the >> program exits. The original changes to uptime had a few other issues, >> which I fixed. >> > > Is there a list of tools that can already output via libxo? Neither > "uptime -h", nor its manpage or "apropros libxo" doesn't reveal > anything. i was going to suggest doing ldd on the binaries or a grep on the Makefile but the latter returns a surprisingly low number of matches. > grep lxo */*/Makefile* rescue/rescue/Makefile:CRUNCH_LIBS+= -lcrypt -ledit -ljail -lkvm -ll -ltermcapw -lutil -lxo tools/bsdbox/Makefile:CRUNCH_SHLIBS+= -lc -lutil -lcrypt -lxo -lgpio perhaps cheers luigi