From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] New package: socketcand
Date: Fri, 23 Mar 2012 10:06:40 +0100 [thread overview]
Message-ID: <4F6C3D20.8050304@visionsystems.de> (raw)
In-Reply-To: <20120323095538.5edb8eea@skate>
Am 23.03.2012 09:55, schrieb Thomas Petazzoni:
> Le Thu, 22 Mar 2012 23:54:34 +0100,
> Peter Korsgaard <jacmet@uclibc.org> a ?crit :
>
>>>>>>> "yegorslists" == yegorslists <yegorslists@googlemail.com>
>>>>>>> writes:
>>
>> yegorslists> From: Yegor Yefremov <yegorslists@googlemail.com>
>> yegorslists> Signed-off-by: Yegor Yefremov
>> yegorslists> <yegorslists@googlemail.com>
>>
>> Committed, thanks.
>
> There are apparently build problems with this package:
> http://autobuild.buildroot.org/results/d6a79808eae008611a3ed12a0b7d9901a7fc159f/build-end.log
>
> The host system I use is an old Debian Sarge, so the coreutils
> (including cp) might be quite old. But I think it's a good test to see
> if we can correctly build on old enterprise distros such as RHEL that
> some people are forced to use in companies (and I feel sorry for them).
What do you suggest?
I found following solution here:
http://superuser.com/questions/140708/ubuntu-equivalent-of-unix-command-cp-n
if [ ! -e dest ]; then
cp -f src dest
fi
Yegor
next prev parent reply other threads:[~2012-03-23 9:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 15:00 [Buildroot] [PATCH 1/2] New package: socketcand yegorslists at googlemail.com
2012-03-22 15:01 ` [Buildroot] [PATCH 2/2] udev: bump to 182 yegorslists at googlemail.com
2012-03-22 23:21 ` Peter Korsgaard
2012-03-22 22:54 ` [Buildroot] [PATCH 1/2] New package: socketcand Peter Korsgaard
2012-03-23 8:55 ` Thomas Petazzoni
2012-03-23 9:06 ` Yegor Yefremov [this message]
2012-03-23 9:16 ` Thomas Petazzoni
2012-03-23 9:19 ` Yegor Yefremov
2012-03-27 9:39 ` Thomas Petazzoni
2012-03-27 9:45 ` Yegor Yefremov
2012-03-27 9:54 ` Thomas Petazzoni
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=4F6C3D20.8050304@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--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