headers
Ruben David Fraga Dopico | 1 Apr 20:24
Picon

joe-2.9.8-pre1-1022

cd . \
      && CONFIG_FILES= CONFIG_HEADERS=autoconf.h \
         /bin/sh ./config.status
config.status: creating autoconf.h
config.status: autoconf.h is unchanged
make  all-am
source='b.c' object='b.o' libtool=no \
    depfile='.deps/b.Po' tmpdepfile='.deps/b.TPo' \
    depmode=gcc3 /bin/sh ./depcomp \
    gcc -DHAVE_CONFIG_H -I. -I. -I. -DJOERC="\"/sw/etc/joe/\""  
-I/sw/include  -g -O2 -c `test -f b.c || echo './'`b.c
In file included from b.c:8:
config.h:9:37: error: operator '&&' has no right operand
b.c: In function 'pfind':
b.c:957: warning: pointer targets in passing argument 2 of 'ffind' 
differ in signedness
b.c: In function 'pifind':
b.c:971: warning: pointer targets in passing argument 2 of 'fifind' 
differ in signedness
b.c: In function 'prfind':
b.c:1107: warning: pointer targets in passing argument 2 of 'frfind' 
differ in signedness
b.c: In function 'prifind':
b.c:1121: warning: pointer targets in passing argument 2 of 'frifind' 
differ in signedness
make[1]: *** [b.o] Error 1
make: *** [all] Error 2
### execution of make failed, exit code 2
Removing runtime build-lock...
Removing build-lock package...
(Continue reading)

Permalink | Reply | 1 comment |
headers
Alexander K. Hansen | 1 Apr 20:43
Picon
Gravatar

Re: joe-2.9.8-pre1-1022

On Tuesday 01 April 2008 02:24:51 pm Ruben David Fraga Dopico wrote:
> cd . \
>       && CONFIG_FILES= CONFIG_HEADERS=autoconf.h \
>          /bin/sh ./config.status
> config.status: creating autoconf.h
> config.status: autoconf.h is unchanged
> make  all-am
> source='b.c' object='b.o' libtool=no \
>     depfile='.deps/b.Po' tmpdepfile='.deps/b.TPo' \
>     depmode=gcc3 /bin/sh ./depcomp \
>     gcc -DHAVE_CONFIG_H -I. -I. -I. -DJOERC="\"/sw/etc/joe/\""
> -I/sw/include  -g -O2 -c `test -f b.c || echo './'`b.c
> In file included from b.c:8:
> config.h:9:37: error: operator '&&' has no right operand
> b.c: In function 'pfind':
> b.c:957: warning: pointer targets in passing argument 2 of 'ffind'
> differ in signedness
> b.c: In function 'pifind':
> b.c:971: warning: pointer targets in passing argument 2 of 'fifind'
> differ in signedness
> b.c: In function 'prfind':
> b.c:1107: warning: pointer targets in passing argument 2 of 'frfind'
> differ in signedness
> b.c: In function 'prifind':
> b.c:1121: warning: pointer targets in passing argument 2 of 'frifind'
> differ in signedness
> make[1]: *** [b.o] Error 1
> make: *** [all] Error 2
> ### execution of make failed, exit code 2
> Removing runtime build-lock...
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Macks | 1 Apr 23:24

Re: zope-2.6.3-1104

On Mon, Mar 31, 2008 at 02:59:40PM -0400, Hanspeter Niederstrasser wrote:
> Daniel Macks wrote:
> > On Mon, Mar 31, 2008 at 01:54:10PM -0400, Alexander Hansen wrote:
> >> Pascal Staccini wrote:
> >>> hello
> >>> could it be possible to use python 2.4.4 to compile this release of  
> >>> Zope ?
> >>> this package has been structured to use python 2.4.3 and this seems  
> >>> the wrong version.
> >>> no error during the compiling, but when starting zope, the error is  
> >>> related to python 2.4.3
> >>> see :
http://www.opensubscriber.com/message/fink-users <at> lists.sourceforge.net/8672607.html 
> >>>   for details
> >>> I already posted a similar message one month ago, but no answer
> >>> thank you
> >>> pascal
> >>>
> >>> --
> >>> Package manager version: 0.28.1
> >>> Distribution version: selfupdate-rsync Sun Mar 30 21:25:59 2008, 10.5,  
> >>> i386
> >>> Mac OS X version: 10.5.2
> >>> Xcode version: 3.0
> >>> gcc version: 4.0.1 (Apple Inc. build 5465)
> >>> make version: 3.81
> >>> Feedback Courtesy of FinkCommander
> >>>   
> >> The issue is really "can python24 be updated to  Python-2.4.4?"  You'll 
> >> be best served emailing the maintainer of python24 about this.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ray Zimmerman | 2 Apr 16:26
Picon
Favicon

g95-0.90-3

There is a bug in g95 0.90 that is affecting me and I'm told it's  
fixed in 0.91. Is there any chance that whoever put together the fink  
package for 0.90 could update it to 0.91? I see I'm not the only one  
interested in this
(http://www.mail-archive.com/fink-beginners <at> lists.sourceforge.net/msg21103.html 
).

Thanks,

-- 
Ray Zimmerman
Senior Research Associate
428-B Phillips Hall, Cornell University, Ithaca, NY 14853
phone: (607) 255-9645

--
Package manager version: 0.28.1
Distribution version: selfupdate-rsync Mon Mar 31 16:25:19 2008, 10.5,  
i386
Mac OS X version: 10.5.2
Xcode version: 3.0
gcc version: 4.0.1 (Apple Inc. build 5465)
make version: 3.81
Feedback Courtesy of FinkCommander

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
(Continue reading)

Permalink | Reply | 4 comments |
headers
Alexander Hansen | 2 Apr 19:10
Picon
Gravatar

Re: g95-0.90-3

Ray Zimmerman wrote:
> There is a bug in g95 0.90 that is affecting me and I'm told it's  
> fixed in 0.91. Is there any chance that whoever put together the fink  
> package for 0.90 could update it to 0.91? I see I'm not the only one  
> interested in this
(http://www.mail-archive.com/fink-beginners <at> lists.sourceforge.net/msg21103.html 
> ).
>
> Thanks,
>
>   
The person who maintained g95 for a long time has retired from Fink, 
which is why the package maintainer email contact is this list.  An 
update would require somebody else to step in and do it. 

For a shorter-term option:  can what you're working on use gfortran (via 
our gcc42 or gcc43 packages) instead?

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
Permalink | Reply | 3 comments |
headers
James Bunton | 3 Apr 12:54
Favicon

Re: Updated mplayer (#1885675)

On Wed, Feb 27, 2008 at 07:20:39AM +1100, James Bunton wrote:
> Hi,
> 
> Apologies for the cross-post to fink-users, hit the wrong address book entry :\
> 
> See this tracker item:
> https://sourceforge.net/tracker/?func=detail&atid=414256&aid=1885674&group_id=17203
> 
> I contacted the listed maintainer on Feb 14th 2008 and have not received a
> response. Could the tracker item please be reopened and the package
> reconsidered for entry in Fink?
> 
> I'm willing to step up as the maintainer and keep up with new releases, etc.
> Also, this package has been confirmed to build on 10.5 PPC and Intel with all
> validation passing.

Hello again,

Alex Hansen suggested I'd be better off discussing the package here on
fink-devel.

The latest version of the info files can be found here:
http://delx.net.au/files/finkinfos

mplayer has been updated to 1.0rc2 with all available security patches. It
also builds on 10.4 & 10.5 on Intel and PPC.

libdvdnav has been modified to use the newest version of libdvdread in fink.

The only change to libx264-57-shlibs.info is to remove the dependency on
(Continue reading)

Permalink | Reply | 8 comments |
headers
Ray Zimmerman | 4 Apr 16:14
Picon
Favicon

Re: g95-0.90-3

On Apr 2, 2008, at 1:10 PM, Alexander Hansen wrote:

> Ray Zimmerman wrote:
>> There is a bug in g95 0.90 that is affecting me and I'm told it's   
>> fixed in 0.91. Is there any chance that whoever put together the  
>> fink  package for 0.90 could update it to 0.91? I see I'm not the  
>> only one  interested in this
(http://www.mail-archive.com/fink-beginners <at> lists.sourceforge.net/msg21103.html 
>>  ).
>>
>> Thanks,
>>
>>
> The person who maintained g95 for a long time has retired from Fink,  
> which is why the package maintainer email contact is this list.  An  
> update would require somebody else to step in and do it.
> For a shorter-term option:  can what you're working on use gfortran  
> (via our gcc42 or gcc43 packages) instead?

Well, sort of ... and that's exactly what I had already tried.  
Unfortunately, my project (a Matlab MEX file) built with gfortan has  
some other minor issues I've been unable to resolve. I welcome any  
suggestions for resolving the following ...

1. It wants to link against the dynamic libgfortran preventing my MEX  
file from working on machines that don't have gfortran installed. The  
only way I can get it to link against the static libgfortran is to  
hide the .dylib file during linking. Using the -static-libgfortran  
option to the linker appears to have no effect.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Alexander Hansen | 4 Apr 16:32
Picon
Gravatar

Re: g95-0.90-3

Ray Zimmerman wrote:
> On Apr 2, 2008, at 1:10 PM, Alexander Hansen wrote:
>
>   
>> Ray Zimmerman wrote:
>>     
>>> There is a bug in g95 0.90 that is affecting me and I'm told it's   
>>> fixed in 0.91. Is there any chance that whoever put together the  
>>> fink  package for 0.90 could update it to 0.91? I see I'm not the  
>>> only one  interested in this
(http://www.mail-archive.com/fink-beginners <at> lists.sourceforge.net/msg21103.html 
>>>  ).
>>>
>>> Thanks,
>>>
>>>
>>>       
>> The person who maintained g95 for a long time has retired from Fink,  
>> which is why the package maintainer email contact is this list.  An  
>> update would require somebody else to step in and do it.
>> For a shorter-term option:  can what you're working on use gfortran  
>> (via our gcc42 or gcc43 packages) instead?
>>     
>
> Well, sort of ... and that's exactly what I had already tried.  
> Unfortunately, my project (a Matlab MEX file) built with gfortan has  
> some other minor issues I've been unable to resolve. I welcome any  
> suggestions for resolving the following ...
>
> 1. It wants to link against the dynamic libgfortran preventing my MEX
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ray Zimmerman | 4 Apr 17:55
Picon
Favicon

Re: g95-0.90-3


On Apr 4, 2008, at 10:32 AM, Alexander Hansen wrote:
> Ray Zimmerman wrote:
>>
>> 1. It wants to link against the dynamic libgfortran preventing my  
>> MEX  file from working on machines that don't have gfortran  
>> installed. The  only way I can get it to link against the static  
>> libgfortran is to  hide the .dylib file during linking. Using the - 
>> static-libgfortran  option to the linker appears to have no effect.
>>
>> 2. It can't seem to find the 'dtime' symbol, even though it appears  
>> to  exist in libgfortran.
>>
>> 3. When running Matlab from the Terminal, I can build a Fortran  
>> MEX  file that works, but after running it and exiting Matlab,  
>> input is no  longer echoed to the screen in the Terminal session. I  
>> can execute  commands, but my typing is not echoed. I can even  
>> restart Matlab and  input at the Matlab prompt *is* echoed, but the  
>> problem returns as  soon as I quit Matlab.
>>
>>  Thanks.
>>
>>
> Ah.  #1 is an issue that has shown up pretty often.  I'll try to  
> scrape some time together this weekend and see if the 0.91 upgrade  
> will be easy or not.

With a bit more work, I resolved #2 (there was a unnecessary 'external  
dtime' line in the code) and for #1 I found that explicitly passing / 
sw/lib/gcc4.3/lib/libgfortran.a to the linker also worked. But #3 is
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jack Howarth | 5 Apr 04:50
Picon
Gravatar

pdftk update

   I've updated pdftk in fink unstable to the latest 1.41 release
for Matthias Ringwald. In case anyone is wondering why we left the
package building against gcc42, the reason is that the upstream
code is actually broken and just happens to work under prior releases.
The author of the pdftk is incorrectly using c++ i/o with java
exceptions. This is (correctly) rejected by the g++ compiler now
as of gcc 4.3.0 and thus pdftk.cc can no longer be compiled. The
gcc developers where quite shocked that resulting code even
worked under prior gcc releases. However this might explain
why the author had to limit the gcj compiler flags to -O2
(for at least gcc 3.4.4).
                   Jack

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
Permalink | Reply | 8 comments |

Gmane