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 0000196]: libelf-0.8.5 wrong location
Date: Mon, 12 Feb 2007 05:51:06 -0800	[thread overview]
Message-ID: <49c79d1298e28cdc5c04024bde9baaeb@bugs.busybox.net> (raw)


The following issue has been ASSIGNED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=196 
====================================================================== 
Reported By:                Oliv
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   196
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             03-29-2005 07:53 PST
Last Modified:              02-12-2007 05:51 PST
====================================================================== 
Summary:                    libelf-0.8.5 wrong location
Description: 
when wget tries to retrieve libelf an error occurs 'cause his location has
changed:
wget --passive-ftp -P /data/LiveCD/buildroot/dl
http://www.stud.uni-hannover.de/~michael/software//libelf-0.8.5.tar.gz
--17:47:30-- 
http://www.stud.uni-hannover.de/%7Emichael/software/libelf-0.8.5.tar.gz
           => `/data/LiveCD/buildroot/dl/libelf-0.8.5.tar.gz'
R?solution de www.stud.uni-hannover.de... 130.75.176.2
Connexion vers www.stud.uni-hannover.de[130.75.176.2]:80...connect?.
requ?te HTTP transmise, en attente de la r?ponse...404 Not Found
17:47:30 ERREUR 404: Not Found.

make: *** [/data/LiveCD/buildroot/dl/libelf-0.8.5.tar.gz] Erreur 1


the "new" URL is: http://www.mr511.de/software/
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0000179 libelf Source URI is broken
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-29-05 07:53  Oliv           New Issue                                    
03-29-05 12:11  vapier         Relationship added       duplicate of 0000179
03-29-05 12:11  vapier         Duplicate ID             0 => 179            
03-29-05 12:11  vapier         Status                   assigned => resolved
03-29-05 12:11  vapier         Resolution               open => duplicate   
04-12-05 15:05  andersen       Status                   resolved => closed  
02-12-07 05:51  vapier         Status                   closed => assigned  
02-12-07 05:51  vapier         Assigned To              uClibc => buildroot 
======================================================================

                 reply	other threads:[~2007-02-12 13:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=49c79d1298e28cdc5c04024bde9baaeb@bugs.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