libexif-devel — This is the place where your questions about libexif will be answered.

[Libexif-devel] New French PO file for 'exif' (version 0.6.20)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'exif' has been submitted
by the French team of translators.  The file is available at:

    http://translationproject.org/latest/exif/fr.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/exif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/exif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New French PO file for 'libexif' (version 0.6.21-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the French team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/fr.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] libexif test suite updated

[Dan F. <da...@co...>]

For those who are interested, I've added some tests to the
libexif-testsuite that can be used to reproduce some of the security
issues fixed in yesterday's release. Most of the new tests only show
problems in 64-bit environments, and many will only actually show
problems if run with valgrind or another memory sanitization framework.
You can use valgrind by manually editing tests/check-vars.sh once the
test suite is configured to change EXIFEXE to something like:

EXIFEXE="valgrind --leak-check=full --log-file=exif --error-exitcode=127 \
         $TOPBLDDIR/src/exif/exif/exif"

This will cause check-exif-executable.sh to fail, but will run
valgrind on the rest and fail the tests (most of the tests, anyway) if
something suspicious happens.

And in case you're not aware, both the libexif and exif packages include
small self-contained test suites. Just run 'make check' after a build
and it will run some quick sanity checks without having to install the
full test suite and all its dependencies.

>>> Dan

[Libexif-devel] libexif project security advisory July 12, 2012

[Dan F. <da...@co...>]

libexif project security advisory
July 12, 2012

PROBLEM DESCRIPTION

A number of remotely exploitable issues were discovered in libexif
and exif, with effects ranging from information leakage to potential
remote code execution. The issues are:

CVE-2012-2812: A heap-based out-of-bounds array read in the
exif_entry_get_value function in libexif/exif-entry.c in libexif 0.6.20
and earlier allows remote attackers to cause a denial of service or
possibly obtain potentially sensitive information from process memory
via an image with crafted EXIF tags.

CVE-2012-2813: A heap-based out-of-bounds array read in the
exif_convert_utf16_to_utf8 function in libexif/exif-entry.c in libexif
0.6.20 and earlier allows remote attackers to cause a denial of service
or possibly obtain potentially sensitive information from process
memory via an image with crafted EXIF tags. 

CVE-2012-2814: A buffer overflow in the exif_entry_format_value function
in libexif/exif-entry.c in libexif 0.6.20 allows remote attackers to
cause a denial of service or possibly execute arbitrary code via an
image with crafted EXIF tags.

CVE-2012-2836: A heap-based out-of-bounds array read in the
exif_data_load_data function in libexif 0.6.20 and earlier allows remote
attackers to cause a denial of service or possibly obtain potentially
sensitive information from process memory via an image with crafted
EXIF tags.

CVE-2012-2837: A divide-by-zero error in the
mnote_olympus_entry_get_value function while formatting EXIF maker note
tags in libexif 0.6.20 and earlier allows remote attackers to cause a
denial of service via an image with crafted EXIF tags.

CVE-2012-2840: An off-by-one error in the exif_convert_utf16_to_utf8
function in libexif/exif-entry.c in libexif 0.6.20 and earlier allows
remote attackers to cause a denial of service or possibly execute
arbitrary code via an image with crafted EXIF tags. 

CVE-2012-2841: An integer underflow in the exif_entry_get_value function
can cause a heap overflow and potentially arbitrary code execution while
formatting an EXIF tag, if the function is called with a buffer size
parameter equal to zero or one.

CVE-2012-2845: An integer overflow in the function jpeg_data_load_data
in the exif program could cause a data read beyond the end of a buffer,
causing an application crash or leakage of potentially sensitive
information when parsing a crafted JPEG file.

There are no known public exploits of these issues.

AFFECTED VERSIONS

All of the described vulnerabilities affect libexif
version 0.6.20, and most affect earlier versions as well.

SOLUTION

Upgrade to version 0.6.21 which is not vulnerable to
these issues.

CHECKSUMS

Here are the MD5 sums of the released files:

0e744471b8c3b3b1534d5af38bbf6408  exif-0.6.21.tar.bz2
78b9f501fc19c6690ebd655385cd5ad6  exif-0.6.21.tar.gz
27339b89850f28c8f1c237f233e05b27  libexif-0.6.21.tar.bz2
9321c409a3e588d4a99d63063ef4bbb7  libexif-0.6.21.tar.gz
aa208b40c853792ba57fbdc1eafcdc95  libexif-0.6.21.zip

Here are the SHA1 sums of the released files:

74652e3d04d0faf9ab856949d7463988f0394db8  exif-0.6.21.tar.bz2
d23139d26226b70c66d035bbc64482792c9f1101  exif-0.6.21.tar.gz
a52219b12dbc8d33fc096468591170fda71316c0  libexif-0.6.21.tar.bz2
4106f02eb5f075da4594769b04c87f59e9f3b931  libexif-0.6.21.tar.gz
e5990860e9ec5a6aedde0552507a583afa989ca2  libexif-0.6.21.zip

ACKNOWLEDGEMENTS

Mateusz Jurczyk of Google Security Team reported the issues
CVE-2012-2812, CVE-2012-2813 and CVE-2012-2814. Yunho Kim reported the
issues CVE-2012-2836 and CVE-2012-2837. Dan Fandrich discovered the
issues CVE-2012-2840, CVE-2012-2841 and CVE-2012-2845.

REFERENCES

http://libexif.sf.net

[Libexif-devel] libexif and exif 0.6.21 released

[Dan F. <da...@co...>]

This release fixes a number of potentially serious security issues.

libexif-0.6.21 (2012-07-12):
  * New translations: en_AU, uk
  * Updated translations: cs, da, de, en_CA, nl, pl, sk, sv, vi
  * Added more supported lenses in Canon MakerNote
  * Added some defensive NULL pointer checks
  * Fixed a number of security and stability issues due to buffer overflows,
    bad pointer dereferences and division-by-zero including bug #3434540
    and bug #3434545 (CVE-2012-2812, CVE-2012-2813, CVE-2012-2814,
    CVE-2012-2836, CVE-2012-2837, CVE-2012-2840, CVE-2012-2841,
    CVE-2012-2845)

exif-0.6.21 (2012-07-12):
  * New translations: cs, eo, hr, sr, uk
  * Updated translations: da, de, fi, id, is, it, nl, pl, sk, sv, vi, zh_CN
  * Improved the man page
  * Prevent NULL pointer dereference on out of memory situation
  * Fixed bug that caused read past the end of a buffer (CVE-2012-2845)

Here are the SHA1 sums of the released files:

74652e3d04d0faf9ab856949d7463988f0394db8  exif-0.6.21.tar.bz2
d23139d26226b70c66d035bbc64482792c9f1101  exif-0.6.21.tar.gz
a52219b12dbc8d33fc096468591170fda71316c0  libexif-0.6.21.tar.bz2
4106f02eb5f075da4594769b04c87f59e9f3b931  libexif-0.6.21.tar.gz
e5990860e9ec5a6aedde0552507a583afa989ca2  libexif-0.6.21.zip

They are available for download at
https://sourceforge.net/projects/libexif/files/

>>> Dan

Re: [Libexif-devel] CVS mails no longer sent

[Jan P. <pa...@pi...>]

> On Wed, Jul 11, 2012 at 11:12:34PM +0200, Dan Fandrich wrote:
>> The attached patch should fix it, but I don't seem to have
>> permissions to write to that directory. Maybe Hans can do it.
>
> I figured out the issue with submitting the change and have now done it.
> We'll see if the mails start flowing again.
>
>>>> Dan

Great! Thanks!

 --- Jan

Re: [Libexif-devel] CVS mails no longer sent

[Dan F. <da...@co...>]

On Wed, Jul 11, 2012 at 07:14:15AM +0200, Jan Patera wrote:
> I just noticed I am no longer receiving CVS mails about submits to libexif
> -> not noticing people (=Dan ;-)) doing updates.
> Even the maillist archive has no updates for year and half.

Now that you mention it, I haven't either. But, there hasn't been much
activity the last while and I had it set to digest mode, so I didn't
really clue in.

> I just did a submit and it ended with the following:
> 
> /cvsroot/libexif/libexif/libexif/exif-entry.c,v  <--  exif-entry.c
> new revision: 1.145; previous revision: 1.144
> done
> # The libexif project will migrate from CVS to SVN or something bette
> # some time. We don't know any details yet, though. (2007-05-21)
> Notifying #gphoto...done.
> Mailing lib...@li......
> Generating notification message...
> Generating notification message... done.
> Mailing lib...@li......
> Generating notification message...
> Traceback (most recent call last):
>   File "/cvsroot/libexif/CVSROOT/syncmail", line 447, in ?
>     main()
>   File "/cvsroot/libexif/CVSROOT/syncmail", line 440, in main
>     contextlines, fromhost, replyto, showcfunction)
>   File "/cvsroot/libexif/CVSROOT/syncmail", line 231, in blast_mail
>     conn.connect(MAILHOST, MAILPORT)
>   File "/usr/lib64/python2.4/smtplib.py", line 306, in connect
>     raise socket.error, msg
> socket.error: (111, 'Connection refused')
> 
> Any idea what the problem is and who can fix it?

I've noticed this myself, but couldn't figure out how to access the
mail configuration. On a hunch, I just tried checking out an invisible
libexif project called 'CVSROOT' from CVS, and it worked--I now have the
files, but I don't know how to fix it. I don't see any SMTP server
configuration in there, just an e-mail address. My guess is that
SourceForge tightened security on their CVS servers and is no longer
allowing outgoing network connections.

I just found a SourceForge ticket on this issue:
https://sourceforge.net/apps/trac/sourceforge/ticket/20300
The attached patch should fix it, but I don't seem to have
permissions to write to that directory. Maybe Hans can do it.

>>> Dan

Re: [Libexif-devel] CVS mails no longer sent

[Dan F. <da...@co...>]

On Wed, Jul 11, 2012 at 11:12:34PM +0200, Dan Fandrich wrote:
> The attached patch should fix it, but I don't seem to have
> permissions to write to that directory. Maybe Hans can do it.

I figured out the issue with submitting the change and have now done it.
We'll see if the mails start flowing again.

>>> Dan

[Libexif-devel] CVS mails no longer sent

[Jan P. <pa...@pi...>]

Hi all,

I just noticed I am no longer receiving CVS mails about submits to libexif
-> not noticing people (=Dan ;-)) doing updates.
Even the maillist archive has no updates for year and half.

I just did a submit and it ended with the following:

/cvsroot/libexif/libexif/libexif/exif-entry.c,v  <--  exif-entry.c
new revision: 1.145; previous revision: 1.144
done
# The libexif project will migrate from CVS to SVN or something bette
# some time. We don't know any details yet, though. (2007-05-21)
Notifying #gphoto...done.
Mailing lib...@li......
Generating notification message...
Generating notification message... done.
Mailing lib...@li......
Generating notification message...
Traceback (most recent call last):
  File "/cvsroot/libexif/CVSROOT/syncmail", line 447, in ?
    main()
  File "/cvsroot/libexif/CVSROOT/syncmail", line 440, in main
    contextlines, fromhost, replyto, showcfunction)
  File "/cvsroot/libexif/CVSROOT/syncmail", line 231, in blast_mail
    conn.connect(MAILHOST, MAILPORT)
  File "/usr/lib64/python2.4/smtplib.py", line 306, in connect
    raise socket.error, msg
socket.error: (111, 'Connection refused')

Any idea what the problem is and who can fix it?

 --- Jan

[Libexif-devel] New German PO file for 'libexif' (version 0.6.21-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the German team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/de.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Danish PO file for 'libexif' (version 0.6.21-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the Danish team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/da.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Ukrainian PO file for 'libexif' (version 0.6.21-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the Ukrainian team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/uk.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Ukrainian PO file for 'exif' (version 0.6.20)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'exif' has been submitted
by the Ukrainian team of translators.  The file is available at:

    http://translationproject.org/latest/exif/uk.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/exif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/exif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Vietnamese PO file for 'libexif' (version 0.6.21-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the Vietnamese team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/vi.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Slovak PO file for 'libexif' (version 0.6.21-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the Slovak team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/sk.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Polish PO file for 'libexif' (version 0.6.21-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the Polish team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/pl.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Ukrainian PO file for 'libexif' (version 0.6.21-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the Ukrainian team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/uk.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New template for 'libexif' made available

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.  (If you have
any questions, send them to <coo...@tr...>.)

A new POT file for textual domain 'libexif' has been made available
to the language teams for translation.  It is archived as:

    http://translationproject.org/POT-files/libexif-0.6.21-pre1.pot

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

Below is the URL which has been provided to the translators of your
package.  Please inform the translation coordinator, at the address
at the bottom, if this information is not current:

    http://sourceforge.net/projects/libexif/files/libexif/prerelease/libexif-0.6.21-pre1.tar.gz

We can arrange things so that translated PO files are automatically e-mailed
to you when they arrive.  Ask at the address below if you want this.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

Re: [Libexif-devel] Building libexif in MSVS 2008

[Dan F. <da...@co...>]

On Wed, May 23, 2012 at 06:36:55PM -0700, exif par wrote:
> Using autoconf, I was able to generate a config file. I renamed some of the
> basic C header files such as sys/types.h, stdint.h, libintl.h to simulate the
> MSVS building environment. In this build environment, config.h is not generated
> correctly. In MSVS 2008, "inline", "snprintf" and "size_t" keywords are not
> defined. We need to provide those definitions as follows:
> 
> #define inline __inline
> #define snprintf _snprintf
> typedef int64_t           ssize_t;
> 
> Can autoconf generate these #define's?

autoconf should be defining the first and last of these (although, not
the way you have done). snprintf is C99, so it should exist--there's no
workaround when it doesn't.  There shouldn't be any references to
stdint.h and libintl.h if they doen't exist--sys/types.h is pretty commonly
available, but it's only used in one place in the code so we could work
around not having it. You should be able to tell from config.log why the
others aren't being generated properly.

>>> Dan

Re: [Libexif-devel] Building libexif in MSVS 2008

[exif p. <exi...@gm...>]

Using autoconf, I was able to generate a config file. I renamed some of the
basic C header files such as sys/types.h, stdint.h, libintl.h to simulate
the MSVS building environment. In this build environment, config.h is not
generated correctly. In MSVS 2008, "inline", "snprintf" and "size_t"
keywords are not defined. We need to provide those definitions as follows:

#define inline __inline
#define snprintf _snprintf
typedef int64_t           ssize_t;

Can autoconf generate these #define's?

Thanks.

On Wed, May 23, 2012 at 3:50 PM, Dan Fandrich <da...@co...>wrote:

> On Wed, May 23, 2012 at 03:45:42PM -0700, exif par wrote:
> > In order to work around this problem, I did a bunch of typedef to declare
> > int8_t, uint8_t, etc. It is not only stdint.h but also libintl.h and
> undefined
> > reference to ssize_t.  I am currently trying to build using cygwin. Can
> you
> > tell me the host name for cygwin which I need to pass to ./configure
> script?
>
> You should be having an easier time with Cygwin. I'm not sure what
> --host option you would need, but you should probably be able to just do
> "./configure CC=cygwin-gcc" (giving the correct name of the cygwin
> compiler)
> and autoconf should automagically figure it all out.  You should not be
> seeing references to libintl.h or stdint.h if they don't exist, if
> autoconf has done its job correctly.
>
> >>> Dan
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> libexif-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libexif-devel
>

Re: [Libexif-devel] Building libexif in MSVS 2008

[Dan F. <da...@co...>]

On Wed, May 23, 2012 at 03:45:42PM -0700, exif par wrote:
> In order to work around this problem, I did a bunch of typedef to declare
> int8_t, uint8_t, etc. It is not only stdint.h but also libintl.h and undefined
> reference to ssize_t.  I am currently trying to build using cygwin. Can you
> tell me the host name for cygwin which I need to pass to ./configure script?

You should be having an easier time with Cygwin. I'm not sure what
--host option you would need, but you should probably be able to just do
"./configure CC=cygwin-gcc" (giving the correct name of the cygwin compiler)
and autoconf should automagically figure it all out.  You should not be
seeing references to libintl.h or stdint.h if they don't exist, if
autoconf has done its job correctly.

>>> Dan

Re: [Libexif-devel] Building libexif in MSVS 2008

[exif p. <exi...@gm...>]

On Wed, May 23, 2012 at 2:58 PM, Dan Fandrich <da...@co...>wrote:

> On Wed, May 23, 2012 at 02:43:11PM -0700, exif par wrote:
> > I am trying to build libexif on MSVS 2008. While trying to compile the
> source
> > code, I get several compilation errors because of missing header files
> such as
> > stdint.h. MSVS 2008 is a common built system. Why is it not supported?
>
> Probably because since 2008, you're the first one to try :-)  Seriously,
> if you find an issue with a compiler, we'd be happy to try accept
> reasonable patches to make it work. libexif has very few external
> dependencies, so it should just work about any standard C system.
> stdint.h has been a standard C header file for over 10 years, so if MSVS
> 2008 doesn't support it, then I'd consider it broken. However, libexif's
> autoconf will create a _stdint.h file automatically to work around such
> broken systems, as long as they can run autoconf, naturally. In your
> case, try just creating a file libexif/_stdint.h containing the single
> line:
>
> #include <stdint.h>
>
> That should be enough to get around this problem.
>

In order to work around this problem, I did a bunch of typedef to declare
int8_t, uint8_t, etc. It is not only stdint.h but also libintl.h and
undefined reference to ssize_t.  I am currently trying to build using
cygwin. Can you tell me the host name for cygwin which I need to pass to
./configure script?

Thanks.

>
> >>> Dan
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> libexif-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libexif-devel
>

Re: [Libexif-devel] Building libexif in MSVS 2008

[Dan F. <da...@co...>]

On Wed, May 23, 2012 at 02:43:11PM -0700, exif par wrote:
> I am trying to build libexif on MSVS 2008. While trying to compile the source
> code, I get several compilation errors because of missing header files such as
> stdint.h. MSVS 2008 is a common built system. Why is it not supported?

Probably because since 2008, you're the first one to try :-)  Seriously,
if you find an issue with a compiler, we'd be happy to try accept
reasonable patches to make it work. libexif has very few external
dependencies, so it should just work about any standard C system.
stdint.h has been a standard C header file for over 10 years, so if MSVS
2008 doesn't support it, then I'd consider it broken. However, libexif's
autoconf will create a _stdint.h file automatically to work around such
broken systems, as long as they can run autoconf, naturally. In your
case, try just creating a file libexif/_stdint.h containing the single
line:

#include <stdint.h>

That should be enough to get around this problem.

>>> Dan

[Libexif-devel] Building libexif in MSVS 2008

[exif p. <exi...@gm...>]

Hello,

I am trying to build libexif on MSVS 2008. While trying to compile the
source code, I get several compilation errors because of missing header
files such as stdint.h. MSVS 2008 is a common built system. Why is it not
supported?

Thanks.

[Libexif-devel] New Indonesian PO file for 'exif' (version 0.6.20)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'exif' has been submitted
by the Indonesian team of translators.  The file is available at:

    http://translationproject.org/latest/exif/id.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/exif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/exif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>