From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/bzip2
Date: Fri, 7 Mar 2008 00:56:09 +0100 [thread overview]
Message-ID: <041901c87fe5$b1503080$030514ac@atmel.com> (raw)
In-Reply-To: 20080306234746.GC26530@cloud.net.au
----- Original Message -----
From: "Hamish Moffatt" <hamish@cloud.net.au>
To: <buildroot@uclibc.org>
Sent: Friday, March 07, 2008 12:47 AM
Subject: Re: [Buildroot] svn commit: trunk/buildroot/package/bzip2
> On Thu, Mar 06, 2008 at 09:56:11AM -0800, ninevoltz at uclibc.org wrote:
>> Author: ninevoltz
>> Date: 2008-03-06 09:56:10 -0800 (Thu, 06 Mar 2008)
>> New Revision: 21184
>>
>> Log:
>> makefile cleanup for bzip2
>>
>> Modified:
>> trunk/buildroot/package/bzip2/bzip2.mk
>>
>>
>> Changeset:
>> Modified: trunk/buildroot/package/bzip2/bzip2.mk
>> ===================================================================
>> --- trunk/buildroot/package/bzip2/bzip2.mk 2008-03-06 17:55:51 UTC (rev 21183)
>> +++ trunk/buildroot/package/bzip2/bzip2.mk 2008-03-06 17:56:10 UTC (rev 21184)
>> @@ -29,7 +29,7 @@
>> $(SED) "s:-O2:$(TARGET_CFLAGS):" $(BZIP2_DIR)/Makefile-libbz2_so
>> touch $@
>>
>> -$(STAGING_DIR)/lib/libbz2.so.$(BZIP2_VERSION): $(BZIP2_DIR)/.unpacked
>> +$(STAGING_DIR)/usr/lib/libbz2.so.$(BZIP2_VERSION): $(BZIP2_DIR)/.unpacked
>
> Why move libbz2 from /lib to /usr/lib?
>
>
I think that this has been the trend for the last year.
A lot of packages has had this change.
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2008-03-06 23:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 17:56 [Buildroot] svn commit: trunk/buildroot/package/bzip2 ninevoltz at uclibc.org
2008-03-06 23:47 ` Hamish Moffatt
2008-03-06 23:56 ` Ulf Samuelsson [this message]
2008-03-07 0:01 ` Hamish Moffatt
2008-03-07 8:24 ` Hans-Christian Egtvedt
-- strict thread matches above, loose matches on Subject: below --
2009-01-20 22:25 ulf at uclibc.org
2007-06-25 14:53 aldot at uclibc.org
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='041901c87fe5$b1503080$030514ac@atmel.com' \
--to=ulf.samuelsson@atmel.com \
--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