From: "Matthew Walker" <mwalker@kydance.net>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Gentoo Linux 1.3a Final Overview
Date: Fri, 14 Jun 2002 13:51:26 -0600 (MDT) [thread overview]
Message-ID: <36764.216.190.203.135.1024084286.squirrel@adamantium.mthmarketing.com> (raw)
In-Reply-To: <200206141544.52651.dougg@ufl.edu>
Read the ebuild for wine. They turn that off on purpose.
<quote who="Doug Goldstein">
> I've noticed in some cases the configs in /etc/make.conf aren't being
> exported.. such as CFLAGS when you try and build wine. A bug maybe? or
> a feature?
>
> -Doug
>
>
> On Friday 14 June 2002 01:33 am, Magnus Therning wrote:
>> I have only done one very quick attempt at installing using the 1.3a
>> tar-ball, at work. the one thing I noticed was that I needed to export
>> 'http_proxy' by hand since all that is supported in the build system
>> is 'HTTP_PROXY', and wget didn't seem to fall back on the uppercase
>> variant if the lowercase variant was missing.
>>
>> /M
>>
>> On Thu, Jun 13, 2002 at 11:03:55AM +0200, Bart Verwilst wrote:
>> > Hi!
>> >
>> > Since Gentoo 1.3a has been available for testing for a little while
>> > now, I've noticed that quite a lot of users installed and tested it,
>> > and i've been swamped by bugreports (to my personal address, the way
>> > i like it, at least for 1.3x issues :o)
>> >
>> > Now, i think most of them have been fixed, including the ncurses one
>> > (grub not compiling and such...), and a few xfree ones..
>> >
>> > I heard though that Xfree had problems compiling with the 'athlon'
>> > flags? Is that correct?
>> >
>> > Now, what this mail is about, i want to get as much info and tips
>> > and bugs into the next one (1.3b), which i'm about to prepare..
>> > So please, speak now, or forever hold your peace :o)
>> >
>> > Send it as a reply to this, and not to my personal mail though!
>> > Things already fixed in my current 1.3b trial version:
>> >
>> > - ncurses prob (new gcc revision (r6))
>> > - 2 bogus accounts on tarballs
>> > - emerge rsync complaining about /etc/make.profile
>> > - .. more, can't seem to remember them :)
>> >
>> >
>> > Please, gimme more! :o)
>> > Thanks in advance
>> >
>> > --
>> > Bart Verwilst
>> > Gentoo Linux Developer, Desktop Team
>> > Gent, Belgium
>> > _______________________________________________
>> > gentoo-dev mailing list
>> > gentoo-dev@gentoo.org
>> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-06-14 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 9:03 [gentoo-dev] Gentoo Linux 1.3a Final Overview Bart Verwilst
2002-06-13 10:01 ` Kim Bratlie
2002-06-13 10:21 ` Bart Verwilst
2002-06-13 12:46 ` Jon Nelson
2002-06-13 15:37 ` Rufiao
2002-06-14 14:25 ` Jean-Michel Smith
2002-06-14 5:33 ` Magnus Therning
2002-06-14 19:44 ` Doug Goldstein
2002-06-14 19:51 ` Matthew Walker [this message]
[not found] <200206131151.21867.verwilst@gentoo.org>
2002-06-13 10:00 ` Will Johansson
2002-06-13 10:04 ` Bart Verwilst
2002-06-13 10:08 ` Brandon Low
2002-06-13 14:59 ` Spider
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=36764.216.190.203.135.1024084286.squirrel@adamantium.mthmarketing.com \
--to=mwalker@kydance.net \
--cc=gentoo-dev@gentoo.org \
/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