Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001257]: Some build targets use hard-coded library names, which causes forced rebuild on Mac OS X
Date: Sat, 2 Jun 2007 01:46:06 -0700	[thread overview]
Message-ID: <5c6eac89d00a6cc00ae8c073c035f913@busybox.net> (raw)


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1257 
====================================================================== 
Reported By:                holin
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1257
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             03-04-2007 05:38 PST
Last Modified:              06-02-2007 01:46 PDT
====================================================================== 
Summary:                    Some build targets use hard-coded library names,
which causes forced rebuild on Mac OS X
Description: 
Library names ending with .so should have .dylib in makefile targets on OS
X. Otherwise, the build system always thinks that the library isn't built
and tries to (re-)build it on every make invocation. Attached a patch that
adds a config option for library filename extension and fixes the packages
that seemed to suffer from this. 
====================================================================== 

---------------------------------------------------------------------- 
 holin - 06-02-07 00:14  
---------------------------------------------------------------------- 
Attached an updated patch for current SVN. Some EXEEXTs would probably be
needed in binutils.mk makerules for Windows hosts. 

---------------------------------------------------------------------- 
 bernhardf - 06-02-07 01:46  
---------------------------------------------------------------------- 
You have to use LIBTGTEXT where possible (i.e. in packages that can be
built as static or dynamic library). See the toplevel Makefile for
LIBTGTEXT.

Please update the patch accordingly.
thanks, 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-04-07 05:38  holin          New Issue                                    
03-04-07 05:38  holin          Status                   new => assigned     
03-04-07 05:38  holin          Assigned To               => buildroot       
03-04-07 05:38  holin          File Added: buildroot-070304-dlext.patch         
          
03-31-07 09:43  bendiken       Issue Monitored: bendiken                    
06-02-07 00:13  holin          File Added: buildroot-070602-dlext-v2.patch      
             
06-02-07 00:14  holin          Note Added: 0002427                          
06-02-07 01:46  bernhardf      Note Added: 0002428                          
======================================================================

             reply	other threads:[~2007-06-02  8:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02  8:46 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-24  7:43 [Buildroot] [buildroot 0001257]: Some build targets use hard-coded library names, which causes forced rebuild on Mac OS X bugs at busybox.net
2007-06-03  7:41 bugs at busybox.net
2007-06-02 11:23 bugs at busybox.net
2007-06-02 10:35 bugs at busybox.net
2007-06-02 10:18 bugs at busybox.net
2007-06-02 10:16 bugs at busybox.net
2007-06-02  9:25 bugs at busybox.net
2007-06-02  9:07 bugs at busybox.net
2007-06-02  9:01 bugs at busybox.net
2007-06-02  7:14 bugs at busybox.net
2007-03-04 13:38 bugs at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5c6eac89d00a6cc00ae8c073c035f913@busybox.net \
    --to=bugs@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox