From owner-freebsd-current Thu Jun 11 07:02:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21528 for freebsd-current-outgoing; Thu, 11 Jun 1998 07:02:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA21522 for ; Thu, 11 Jun 1998 07:02:39 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 9735 invoked from network); 11 Jun 1998 14:02:36 -0000 Received: from usera750.uk.uudial.com (HELO jfsebastian) (193.149.68.242) by smtp.dial.pipex.com with SMTP; 11 Jun 1998 14:02:36 -0000 Message-ID: <002201bd9540$e7852470$0242000a@jfsebastian.k2c.co.uk> From: "Pierre Y. Dampure" To: Subject: Problems building tiff34 Date: Thu, 11 Jun 1998 14:57:42 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure this is really the best place to discuss this, but given that the problem is caused by the recent move towards ELF... ... /usr/ports/graphics/tiff34/patches/patch-aa references /usr/lib/c++rt0, which of course does not reside there any further. It's no problem patching the patch, but obviously that would screw up pre-move -current SNAPs and all past releases. I know this might sound awful, but what about introducing yet another sysctl kern R/O variable, say kern.objformat, specifying where we stand? pre-move -current SNAPs and past releases would not have this variable, anyone building an aout system would have it set to aout, future ELF systems to ELF. It would also make it easier for third-parties... Best Regards, Pierre Y. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message