mailing list of musl libc
 help / color / mirror / code / Atom feed
From: idunham@lavabit.com
To: musl@lists.openwall.com
Subject: Re: libusb, cups compatability...
Date: Wed, 25 Jul 2012 16:17:44 -0700 (PDT)	[thread overview]
Message-ID: <13479.132.241.65.164.1343258264.squirrel@lavabit.com> (raw)
In-Reply-To: <20120725151354.GQ544@brightrain.aerifal.cx>

> On Tue, Jul 24, 2012 at 11:36:38PM -0700, idunham@lavabit.com wrote:
>> I've been needing to set up printing, so I went ahead and compiled
>> libusb
>> 1.0.9 and cups 1.5.3.
>
> Nice.
>
>> libusb needs the  TIMESPEC_TO_TIMEVAL macro; for the time being, I added
>> the definition to libusb (diff attached for Gregor's sake).
>> It probably should go in sys/time.h with gnu | bsd visibility instead.
>> Other than that, libusb compiles.
>
> Is there a corresponding opposite-direction macro that should be
> added?
Yes, TIMEVAL_TO_TIMESPEC. I didn't submit a header patch because I was too
impatient to implement the latter, and figured both should be added at
once.

>> CUPS builds for the most part; in ppdc, genstrings segfaults (haven't
>> built gdb, can't say what the issue is). make || make would finish,
>> though...
>
> This suggests a broken makefile, though most makefiles are broken in
> the same regard... Because the program crashed while writing a target,
> that target, probably corrupted, exists with a valid timestamp and
> causes make to think it doesn't need to be generated the next time
> around. Really, any command in make should move the successfully-built
> file into place _atomically_ (e.g. first writing to a temp file then
> moving it) so this can't happen.

It writes  sample.c (IIRC) which is apparently supposed to contain
localization strings (yes, it builds a C++ file to generate a C file that
has the localization hard-coded inside)...however, the file is empty in
this case.

> Anyway, to get back on-topic, I suspect the generated file was
> incomplete/corrupt and this might be causing problems later down the
> line.
Empty.
This is the main directory that causes trouble during make test; there may
be other issues causing segfaults at both points, however.




      reply	other threads:[~2012-07-25 23:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25  6:36 idunham
2012-07-25 15:13 ` Rich Felker
2012-07-25 23:17   ` idunham [this message]

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=13479.132.241.65.164.1343258264.squirrel@lavabit.com \
    --to=idunham@lavabit.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).