From diy-linux-dev@diy-linux.org  Mon Jul 16 17:41:32 2007
From: diy-linux-dev@diy-linux.org (Pierre Labastie)
Date: Mon, 16 Jul 2007 19:41:32 +0200
Subject: Missing links in tarballs
In-Reply-To: <20070630010920.GA6759@eyo32.local>
References: <20070630010920.GA6759@eyo32.local>
Message-ID: <469BADCC.6020108@club-internet.fr>

Hello,

Looks like man-pages-2.55 has been archived on the kernel site. The 
correct url for it is therefore:
http://www.kernel.org/pub/linux/docs/manpages/Archive/man-pages-2.55.tar.bz2

Alternatively, the refbuild could use the latest 2.62 version...

Regards
Pierre Labastie


From diy-linux-dev@diy-linux.org  Wed Jul 18 00:59:21 2007
From: diy-linux-dev@diy-linux.org (Greg Schafer)
Date: Wed, 18 Jul 2007 10:59:21 +1000
Subject: Missing links in tarballs
In-Reply-To: <469BADCC.6020108@club-internet.fr>
References: <20070630010920.GA6759@eyo32.local> <469BADCC.6020108@club-internet.fr>
Message-ID: <20070718005921.GA20629@eyo32.local>

On Mon, Jul 16, 2007 at 07:41:32PM +0200, Pierre Labastie wrote:

> Looks like man-pages-2.55 has been archived on the kernel site. The 
> correct url for it is therefore:
> http://www.kernel.org/pub/linux/docs/manpages/Archive/man-pages-2.55.tar.bz2
> 
> Alternatively, the refbuild could use the latest 2.62 version...

Yeah, sorry about that. There was some discussion on LKML recently about the
issue. I delayed updating because there was a new Makefile change that
needed a tweaked installation command and testing which is now done. Updated
to 2.62.

Regards
Greg


From diy-linux-dev@diy-linux.org  Mon Jul 23 21:51:27 2007
From: diy-linux-dev@diy-linux.org (Jon Grosshart)
Date: Mon, 23 Jul 2007 17:51:27 -0400
Subject: PPC build on "current"
Message-ID: <9cf823c60707231451k79c22ecbt3d3d6662e6732dbb@mail.gmail.com>

------=_Part_151774_22249611.1185227487842
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hey all. Just a quick 411 on the PPC side using 4.2.1/2.5/2.17/2.6.22.1...
Hardly worth mentioning and takes about 5 seconds to realize a solution
but....

I'm appending -fgnu89-inline to glibc and coreutils else I get thousands of
C99 warnings. I was ignoring it at first but that over doubles your logs
along with creating extra testsuite failures. As it stands now, these are
the only ones I'm getting for glibc.

make[2]: *** [/tmp/glibc-build/stdlib/isomac.out] Error 1
make[2]: *** [/tmp/glibc-build/posix/tst-regex2.out] Error 1

Greg, don't know if you've encountered this with gcc >= 4.1.3 (I think) but
it looks to be manditory on 4.3... I've appended to my build script like so:

case "$DIY_ARCH" in
  i686)   DL=/lib/ld-linux.so.2; MARCH="-march=i686" ;;
  ppc)      DL=/lib/ld.so.1; GNU89="gcc -fgnu89-inline" ;;
  x86_64) DL=/lib64/ld-linux-x86-64.so.2 ;;
esac

And then prepend CC=$GNU89 to ./configure.... Kinda kludgy but doesn't put
up a fuss if CC is empty for the other arches...

Jon

------=_Part_151774_22249611.1185227487842
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hey all. Just a quick 411 on the PPC side using 4.2.1/2.5/2.17/2.6.22.1... Hardly worth mentioning and takes about 5 seconds to realize a solution but....<br><br>I&#39;m appending -fgnu89-inline to glibc and coreutils else I get thousands of C99 warnings. I was ignoring it at first but that over doubles your logs along with creating extra testsuite failures. As it stands now, these are the only ones I&#39;m getting for glibc.
<br><br>make[2]: *** [/tmp/glibc-build/stdlib/isomac.out] Error 1<br>make[2]: *** [/tmp/glibc-build/posix/tst-regex2.out] Error 1<br><br>Greg, don&#39;t know if you&#39;ve encountered this with gcc &gt;= 4.1.3 (I think) but it looks to be manditory on 
4.3... I&#39;ve appended to my build script like so:<br><br>case &quot;$DIY_ARCH&quot; in<br>&nbsp; i686)&nbsp;&nbsp; DL=/lib/ld-linux.so.2; MARCH=&quot;-march=i686&quot; ;;<br>&nbsp; ppc)&nbsp;&nbsp;&nbsp; &nbsp; DL=/lib/ld.so.1; GNU89=&quot;gcc -fgnu89-inline&quot; ;;
<br>&nbsp; x86_64) DL=/lib64/ld-linux-x86-64.so.2 ;;<br>esac<br><br>And then prepend CC=$GNU89 to ./configure.... Kinda kludgy but doesn&#39;t put up a fuss if CC is empty for the other arches...<br><br>Jon<br>

------=_Part_151774_22249611.1185227487842--


From diy-linux-dev@diy-linux.org  Mon Jul 23 23:17:24 2007
From: diy-linux-dev@diy-linux.org (Ryan Hill)
Date: Mon, 23 Jul 2007 17:17:24 -0600
Subject: PPC build on "current"
In-Reply-To: <9cf823c60707231451k79c22ecbt3d3d6662e6732dbb@mail.gmail.com>
References: <9cf823c60707231451k79c22ecbt3d3d6662e6732dbb@mail.gmail.com>
Message-ID: <46A53704.4000703@gentoo.org>

Jon Grosshart wrote:
> Hey all. Just a quick 411 on the PPC side using
> 4.2.1/2.5/2.17/2.6.22.1... Hardly worth mentioning and takes about 5
> seconds to realize a solution but....
> 
> I'm appending -fgnu89-inline to glibc and coreutils else I get thousands
> of C99 warnings. I was ignoring it at first but that over doubles your
> logs along with creating extra testsuite failures. As it stands now,
> these are the only ones I'm getting for glibc.
> 
> make[2]: *** [/tmp/glibc-build/stdlib/isomac.out] Error 1
> make[2]: *** [/tmp/glibc-build/posix/tst-regex2.out] Error 1
> 
> Greg, don't know if you've encountered this with gcc >= 4.1.3 (I think)
> but it looks to be manditory on 4.3... I've appended to my build script
> like so:
> 
> case "$DIY_ARCH" in
>   i686)   DL=/lib/ld-linux.so.2; MARCH="-march=i686" ;;
>   ppc)      DL=/lib/ld.so.1; GNU89="gcc -fgnu89-inline" ;;
>   x86_64) DL=/lib64/ld-linux-x86-64.so.2 ;;
> esac
> 
> And then prepend CC=$GNU89 to ./configure.... Kinda kludgy but doesn't
> put up a fuss if CC is empty for the other arches...

I believe glibc will automatically append -fgnu89-inline if >=gcc-4.2.0
is used to build it.

-- 
dirtyepic    you'd be tossed up or wash up, the narrator relates
 gentoo org          in a spartan antarctican walk for many days
  9B81 6C9F E791 83BB 3AB3  5B2D E625 A073 8379 37E8 (0x837937E8)


From diy-linux-dev@diy-linux.org  Mon Jul 23 23:32:23 2007
From: diy-linux-dev@diy-linux.org (Jon Grosshart)
Date: Mon, 23 Jul 2007 19:32:23 -0400
Subject: PPC build on "current"
In-Reply-To: <46A53704.4000703@gentoo.org>
References: <9cf823c60707231451k79c22ecbt3d3d6662e6732dbb@mail.gmail.com>
 <46A53704.4000703@gentoo.org>
Message-ID: <9cf823c60707231632o7f91adf7w60b8c745e8b81b0@mail.gmail.com>

------=_Part_153306_16681575.1185233543271
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 7/23/07, Ryan Hill <dirtyepic@gentoo.org> wrote:

>
> I believe glibc will automatically append -fgnu89-inline if >=gcc-4.2.0
> is used to build it.



Hmmm.. Doesn't seem to be happening here. I have thousands of these lines in
my glibc log.

 warning: C99 inline functions are not supported; using GNU89

That may be the case when gcc-4.3 goes gold (and results in an error instead
of a warning) but not now.... Atleast not here.. :-)

Jon

------=_Part_153306_16681575.1185233543271
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br><br><div><span class="gmail_quote">On 7/23/07, <b class="gmail_sendername">Ryan Hill</b> &lt;<a href="mailto:dirtyepic@gentoo.org">dirtyepic@gentoo.org</a>&gt; wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>I believe glibc will automatically append -fgnu89-inline if &gt;=gcc-4.2.0<br>is used to build it.</blockquote><div><br><br>Hmmm.. Doesn&#39;t seem to be happening here. I have thousands of these lines in my glibc log.
<br><br>&nbsp;warning: C99 inline functions are not supported; using GNU89<br><br>That may be the case when gcc-4.3 goes gold (and results in an error instead of a warning) but not now.... Atleast not here.. :-)<br><br>Jon<br>
</div><br></div>

------=_Part_153306_16681575.1185233543271--


From diy-linux-dev@diy-linux.org  Tue Jul 24 11:36:31 2007
From: diy-linux-dev@diy-linux.org (Ryan Hill)
Date: Tue, 24 Jul 2007 05:36:31 -0600
Subject: PPC build on "current"
In-Reply-To: <9cf823c60707231632o7f91adf7w60b8c745e8b81b0@mail.gmail.com>
References: <9cf823c60707231451k79c22ecbt3d3d6662e6732dbb@mail.gmail.com>	 <46A53704.4000703@gentoo.org> <9cf823c60707231632o7f91adf7w60b8c745e8b81b0@mail.gmail.com>
Message-ID: <46A5E43F.3060404@gentoo.org>

Jon Grosshart wrote:

> On 7/23/07, *Ryan Hill* <dirtyepic@gentoo.org
> <mailto:dirtyepic@gentoo.org>> wrote:
> 
>     I believe glibc will automatically append -fgnu89-inline if >=gcc-4.2.0
>     is used to build it.
> 
> Hmmm.. Doesn't seem to be happening here. I have thousands of these
> lines in my glibc log.
> 
>  warning: C99 inline functions are not supported; using GNU89
> 
> That may be the case when gcc-4.3 goes gold (and results in an error
> instead of a warning) but not now.... Atleast not here.. :-)

My mistake, it looks like it was added in glibc-2.6.


-- 
dirtyepic    you'd be tossed up or wash up, the narrator relates
 gentoo org          in a spartan antarctican walk for many days
  9B81 6C9F E791 83BB 3AB3  5B2D E625 A073 8379 37E8 (0x837937E8)


From diy-linux-dev@diy-linux.org  Tue Jul 24 14:14:44 2007
From: diy-linux-dev@diy-linux.org (Jon Grosshart)
Date: Tue, 24 Jul 2007 10:14:44 -0400
Subject: PPC build on "current"
In-Reply-To: <46A5E43F.3060404@gentoo.org>
References: <9cf823c60707231451k79c22ecbt3d3d6662e6732dbb@mail.gmail.com>
 <46A53704.4000703@gentoo.org>
 <9cf823c60707231632o7f91adf7w60b8c745e8b81b0@mail.gmail.com>
 <46A5E43F.3060404@gentoo.org>
Message-ID: <9cf823c60707240714q78bd1b1aqf3a34dc709be0ff8@mail.gmail.com>

------=_Part_160015_30694972.1185286484168
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 7/24/07, Ryan Hill <dirtyepic@gentoo.org> wrote:

>
> My mistake, it looks like it was added in glibc-2.6.



Right on. Not sure if this a problem on x86* or not, but this looks to be a
conditional which depends on GLIBC_VER, GCC_VER and possibly DIY_ARCH...
Probably best to not mess with it at all in the ref build. Easy enough to
fix on your own.

Jon

------=_Part_160015_30694972.1185286484168
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br><br><div><span class="gmail_quote">On 7/24/07, <b class="gmail_sendername">Ryan Hill</b> &lt;<a href="mailto:dirtyepic@gentoo.org">dirtyepic@gentoo.org</a>&gt; wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>My mistake, it looks like it was added in glibc-2.6.</blockquote><div><br><br>Right on. Not sure if this a problem on x86* or not, but this looks to be a conditional which depends on GLIBC_VER, GCC_VER and possibly DIY_ARCH... Probably best to not mess with it at all in the ref build. Easy enough to fix on your own.
<br><br>Jon<br></div><br></div>

------=_Part_160015_30694972.1185286484168--