public inbox for gentoo-alpha@lists.gentoo.org
 help / color / mirror / Atom feed
From: jwsacksteder@ramprecision.com
To: gentoo-alpha@gentoo.org
Subject: [gentoo-alpha] Created new bug ticket for issues with I2C
Date: Mon, 13 Oct 2003 22:35:20 -0400	[thread overview]
Message-ID: <71650A6F73F1D411BE8000805F65E3CB3B36AB@SRV-03> (raw)



-----Original Message-----
From: bugzilla-daemon@gentoo.org [mailto:bugzilla-daemon@gentoo.org]
Sent: Monday, October 13, 2003 10:16 PM
To: Jeff Sacksteder
Subject: [Bug 31084] New: i2c ebuild does not build


http://bugs.gentoo.org/show_bug.cgi?id=31084

           Summary: i2c ebuild does not build
           Product: Gentoo Linux
           Version: unspecified
          Platform: Alpha
               URL: http://www.jdfiles.org/i2c_fail.gz
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Ebuilds
        AssignedTo: bug-wranglers@gentoo.org
        ReportedBy: jwsacksteder@ramprecision.com


Trying to get this ebuild into a usable state on Alpha. 

Appears to be a problem with make or bash. [ operator complaining about too
many arguments. Perhaps an extra space somewhere? Full transcript of error
available at URL cited.  Appears to compile, but not install.



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.

--
gentoo-alpha@gentoo.org mailing list


             reply	other threads:[~2003-10-14  2:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14  2:35 jwsacksteder [this message]
2003-10-26  0:58 ` [gentoo-alpha] Created new bug ticket for issues with I2C Aron Griffis
  -- strict thread matches above, loose matches on Subject: below --
2003-10-26 17:50 jwsacksteder

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=71650A6F73F1D411BE8000805F65E3CB3B36AB@SRV-03 \
    --to=jwsacksteder@ramprecision.com \
    --cc=gentoo-alpha@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