Hi Devels,
Please kindly review in the attachment my updated .info files for the
following
packages:
screen:
* add the --enable-colors256 to enable 256 colors terminal support
in GNU screen.
yafc:
* drop readline dependency and switch to readline5
* add --without-krb5,
On Apr 3, 2008, at 6:54 AM, James Bunton wrote:
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:
On Mon, Apr 07, 2008 at 05:59:55AM -0400, Alexander Hansen wrote:
I intended that to mean discussion here, and keeping the submission
up-to-date on the tracker. I tried building the mplayer there again and it
bombed due to a ChangeLog vs. Changelog issue again, because I had
forgotten that
James Bunton wrote:
On Mon, Apr 07, 2008 at 05:59:55AM -0400, Alexander Hansen wrote:
I intended that to mean discussion here, and keeping the submission
up-to-date on the tracker. I tried building the mplayer there again and it
bombed due to a ChangeLog vs. Changelog issue again,
Daniel Macks wrote:
Update of /cvsroot/fink/dists/10.4/unstable/main/finkinfo/sound
In directory
sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv26928/10.4-public/unstable/main/finkinfo/sound
Modified Files:
sdl-sound.info
Log Message:
thanks coreutils + case-insensitive FS!
Index:
Hi list,
I'd like to know where I could upload some (92 meg actually) binaries
i've made today.
here's the list of the packages I'd like to upload
Regards,
Djamé
.//local/injected/binary-darwin-i386/update-packages/rman_3.1-1_darwin-
i386.deb
DJamé Seddah wrote:
Hi list,
I'd like to know where I could upload some (92 meg actually) binaries
i've made today.
here's the list of the packages I'd like to upload
Regards,
Djamé
.//local/injected/binary-darwin-i386/update-packages/rman_3.1-1_darwin-
i386.deb
On 07 Apr 2008, at 23:10, Alexander Hansen wrote:
We don't currently have a mechanism to do this.
At minimum, we would need to check whether contributed binaries don't
have any cross-linking with e.g macports, so that they aren't
immediately broken for users. I don't believe the .deb file
I'm testing a new version of the lpsolve-java package, but it's not
validating because it includes a private library without a Shlibs
declaration. Obviously, the fix is to add the Shlib declaration, but
for some reason it's not working. What I've added looks like this:
Shlibs:
On 08 Apr 2008, at 01:16, Trevor Harmon wrote:
I'm testing a new version of the lpsolve-java package, but it's not
validating because it includes a private library without a Shlibs
declaration. Obviously, the fix is to add the Shlib declaration,
but for some reason it's not working.
On Apr 7, 2008, at 3:37 AM, poppyer wrote:
Hi Devels,
Please kindly review in the attachment my updated .info files for
the following
packages:
screen:
* add the --enable-colors256 to enable 256 colors terminal support
in GNU screen.
yafc:
* drop readline dependency
On Apr 7, 2008, at 7:03 PM, Jean-François Mertens wrote:
On 07 Apr 2008, at 23:10, Alexander Hansen wrote:
We don't currently have a mechanism to do this.
At minimum, we would need to check whether contributed binaries don't
have any cross-linking with e.g macports, so that they aren't
On Apr 7, 2008, at 4:27 PM, Jean-François Mertens wrote:
Try variations..
I remember that originally at least this was extremely sensitive to
spacing..
(conceivably removing the space after the colon, or replacing the
thing by
Shlibs:
!%p/lib/liblpsolve55j.jnilib
with no space at
On Apr 7, 2008, at 7:48 PM, Trevor Harmon wrote:
On Apr 7, 2008, at 4:27 PM, Jean-François Mertens wrote:
Try variations..
I remember that originally at least this was extremely sensitive to
spacing..
(conceivably removing the space after the colon, or replacing the
thing by
Shlibs:
On 08 Apr 2008, at 01:48, Trevor Harmon wrote:
On Apr 7, 2008, at 4:27 PM, Jean-François Mertens wrote:
Try variations..
I remember that originally at least this was extremely sensitive to
spacing..
(conceivably removing the space after the colon, or replacing the
thing by
Shlibs:
On Apr 7, 2008, at 7:16 PM, Trevor Harmon wrote:
I'm testing a new version of the lpsolve-java package, but it's not
validating because it includes a private library without a Shlibs
declaration. Obviously, the fix is to add the Shlib declaration, but
for some reason it's not working. What
On Apr 7, 2008, at 4:56 PM, David Reiser wrote:
Was there any other warning in the build log just prior to the
complaint about the private shlib?
I don't see any warnings at all. The only error is this:
Validating .deb dir /sw/src/fink.build/root-lpsolve-java-5.5.0.11-1...
Error: package
On Apr 7, 2008, at 5:15 PM, Daniel Johnson wrote:
It is indeed a bug, which I've previously reported. The problem is
that the validator is checking the library's install_name but
telling you to use the actual pathname in the error message. These
are not necessarily the same thing. So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trevor Harmon wrote:
| That fixed it. I had to change the Shlibs line from this:
|
| !%p/lib/liblpsolve55j.jnilib
|
| to this:
|
| !liblpsolve55j.jnilib
out of curiosity, what does otool -hv /sw/lib/liblpsolve55j.jnilib
print? It should say it's of
On Apr 7, 2008, at 5:29 PM, Benjamin Reed wrote:
out of curiosity, what does otool -hv /sw/lib/liblpsolve55j.jnilib
print?
$ otool -L /sw/lib/liblpsolve55j.jnilib
/sw/lib/liblpsolve55j.jnilib:
liblpsolve55j.jnilib (compatibility version 5.5.0, current version
5.5.0)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trevor Harmon wrote:
| On Apr 7, 2008, at 5:29 PM, Benjamin Reed wrote:
| out of curiosity, what does otool -hv /sw/lib/liblpsolve55j.jnilib
| print?
|
| $ otool -L /sw/lib/liblpsolve55j.jnilib
not otool -L, otool -hv. =)
- --
Benjamin Reed a.k.a.
Benjamin Reed wrote:
Actually, I just looked; according to
http://developer.apple.com/documentation/Java/Conceptual/Java14Development/05-CoreJavaAPIs/CoreJavaAPIs.html
they allow jnilibs to be dylibs or bundles.
Yes, but it will break if the jnilib is a flat namespace dylib, so if it
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trevor Harmon wrote:
| $ otool -hv /sw/lib/liblpsolve55j.jnilib
| /sw/lib/liblpsolve55j.jnilib:
| Mach header
|magic cputype cpusubtype capsfiletype ncmds
| sizeofcmds flags
| MH_MAGICI386ALL 0x00 DYLIB12
On 08 Apr 2008, at 02:59, Peter O'Gorman wrote:
Benjamin Reed wrote:
Actually, I just looked; according to
http://developer.apple.com/documentation/Java/Conceptual/
Java14Development/05-CoreJavaAPIs/CoreJavaAPIs.html
they allow jnilibs to be dylibs or bundles.
Yes, but it will break if
On Mon, Apr 07, 2008 at 08:15:35PM -0400, Daniel Johnson wrote:
On Apr 7, 2008, at 7:16 PM, Trevor Harmon wrote:
I'm testing a new version of the lpsolve-java package, but it's not
validating because it includes a private library without a Shlibs
declaration. Obviously, the fix is to add
25 matches
Mail list logo