${INSTALL_DATA} problems

[Aristedes Maniatis]

I'm trying to create a port with a command like this:

do-install:
${MKDIR} ${STAGEDIR}${SOLR_HOME}
${INSTALL_DATA} ${WRKSRC}/dist ${STAGEDIR}${SOLR_HOME}

However the output is

/bin/mkdir -p 
/var/poudriere/ports/default/textproc/apache-solr/work/stage/usr/local/solr
install  -m 0644 
/var/poudriere/ports/default/textproc/apache-solr/work/solr-5.5.2/dist 
/var/poudriere/ports/default/textproc/apache-solr/work/stage/usr/local/solr
install: 
/var/poudriere/ports/default/textproc/apache-solr/work/solr-5.5.2/dist: 
Inappropriate file type or format
*** Error code 71

{CP} works fine, but I want to use {INSTALL_DATA} so I can also add the -o flag.


What am I doing wrong?



Please cc me as I'm not on the list.


Thanks
Ari



-- 
-->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ${INSTALL_DATA} problems

[Matthew Seaman]

On 09/08/16 13:27, Aristedes Maniatis wrote:
> I'm trying to create a port with a command like this:
> 
> do-install:
> ${MKDIR} ${STAGEDIR}${SOLR_HOME}
> ${INSTALL_DATA} ${WRKSRC}/dist ${STAGEDIR}${SOLR_HOME}
> 
> However the output is
> 
> /bin/mkdir -p 
> /var/poudriere/ports/default/textproc/apache-solr/work/stage/usr/local/solr
> install  -m 0644 
> /var/poudriere/ports/default/textproc/apache-solr/work/solr-5.5.2/dist 
> /var/poudriere/ports/default/textproc/apache-solr/work/stage/usr/local/solr
> install: 
> /var/poudriere/ports/default/textproc/apache-solr/work/solr-5.5.2/dist: 
> Inappropriate file type or format
> *** Error code 71
> 
> {CP} works fine, but I want to use {INSTALL_DATA} so I can also add the -o 
> flag.
> 
> 
> What am I doing wrong?
> 
> 
> 
> Please cc me as I'm not on the list.

If ${WRKSRC}/dist is a directory and you want to copy it and its
contents recursively into the staging area, then you want one of
COPYTREE_BIN or COPYTREE_SHARE instead of INSTALL_DATA

Cheers,

Matthew




signature.asc
Description: OpenPGP digital signature

Re: ${INSTALL_DATA} problems

[Mathieu Arnold]

Le 08/09/2016 à 14:27, Aristedes Maniatis a écrit :
> I'm trying to create a port with a command like this:
>
> do-install:
> ${MKDIR} ${STAGEDIR}${SOLR_HOME}
> ${INSTALL_DATA} ${WRKSRC}/dist ${STAGEDIR}${SOLR_HOME}
>
> However the output is
>
> /bin/mkdir -p 
> /var/poudriere/ports/default/textproc/apache-solr/work/stage/usr/local/solr
> install  -m 0644 
> /var/poudriere/ports/default/textproc/apache-solr/work/solr-5.5.2/dist 
> /var/poudriere/ports/default/textproc/apache-solr/work/stage/usr/local/solr
> install: 
> /var/poudriere/ports/default/textproc/apache-solr/work/solr-5.5.2/dist: 
> Inappropriate file type or format
> *** Error code 71
>
> {CP} works fine, but I want to use {INSTALL_DATA} so I can also add the -o 
> flag.
>
>
> What am I doing wrong?


Like Matthew said, INSTALL_DATA is for installing one file, not a
directory hierarchy, this is done using COPYTREE_SHARE. As a side not,
we never use CP -R to install files.

Now, I'm seeing something else that is a bad idea, it is using the -o
flag.  Ports must build as a regular user.  A regular user will not be
able to change the owner of the files.  This must be done in the
pkg-plist file, using @owner/@group as described in the Porter's
Handbook:
https://www.freebsd.org/doc/en/books/porters-handbook/plist-keywords.html

--
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Galera

[Sylvain Billon]

Hello,

Galera is not avalaible on the package repo.(freebsd 10)
But on the documentation, it looks that it's possible to install it
with pkg

https://www.freshports.org/databases/galera/

Any information about this ?

Thx
sylvain

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Galera

[Sylvain Billon]

And compilation is not working :)

===>   Returning to build of galera-25.3.5_2
===>   galera-25.3.5_2 depends on package: py27-cloud_sptheme>=0 - not found
===>  py27-cloud_sptheme-1.6_1 is marked as broken: does not build.
*** Error code 1

Sylvain



Le 08/09/2016 à 17:16, Sylvain Billon a écrit :

Hello,

Galera is not avalaible on the package repo.(freebsd 10)
But on the documentation, it looks that it's possible to install it
with pkg

https://www.freshports.org/databases/galera/

Any information about this ?

Thx
sylvain



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Using bsd.prog.mk in source Makefile

[Reid Linnemann]

All,

I'm having issues with an internal port in which the source tree makefile
uses bsd.prog.mk. Using poudriere to build packages as a non-root user, any
targets in the source makefiles which use *OWN and *GRP (such as the
install target) will fail during staging because of an attempt to
chown/chgrp that the non-privileged build user cannot perform. I'm
wondering what the proper resolution for this problem is?

I've tried setting WITH_INSTALL_AS_USER=yes to my port's MAKE_ENV and
BUILD_ENV, and that did not appear to have any effect.

Thanks!

-Reid
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Using bsd.prog.mk in source Makefile

[Mathieu Arnold]

Le 08/09/2016 à 17:38, Reid Linnemann a écrit :
> All,
>
> I'm having issues with an internal port in which the source tree makefile
> uses bsd.prog.mk. Using poudriere to build packages as a non-root user, any
> targets in the source makefiles which use *OWN and *GRP (such as the
> install target) will fail during staging because of an attempt to
> chown/chgrp that the non-privileged build user cannot perform. I'm
> wondering what the proper resolution for this problem is?
>
> I've tried setting WITH_INSTALL_AS_USER=yes to my port's MAKE_ENV and
> BUILD_ENV, and that did not appear to have any effect.

First, let me say that a port should really not use the base system
bsd.prog.mk bsd.lib.mk, and such, because they are moving targets, and
can break your port in no time.

Now, you need to remove all user/groups from the software's Makefile so
that it does not try to chown/grp things, and you must put all the
user/group things in the pkg-plist file using @owner and @group.

-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: Using bsd.prog.mk in source Makefile

[Reid Linnemann]

I really don't want to use autotools for this project, as it is only for a
freebsd product, and bsd.prog.mk and bsd.lib.mk make things very easy,
especially when I want to build and install the project outside of the
context of a port. What alternatives would you suggest? Others in my group
have overridden the do-install port target to avoid invoking the source
install target, but I think that's a little kludgey.

On Thu, Sep 8, 2016 at 9:50 AM, Mathieu Arnold  wrote:

> Le 08/09/2016 à 17:38, Reid Linnemann a écrit :
> > All,
> >
> > I'm having issues with an internal port in which the source tree makefile
> > uses bsd.prog.mk. Using poudriere to build packages as a non-root user,
> any
> > targets in the source makefiles which use *OWN and *GRP (such as the
> > install target) will fail during staging because of an attempt to
> > chown/chgrp that the non-privileged build user cannot perform. I'm
> > wondering what the proper resolution for this problem is?
> >
> > I've tried setting WITH_INSTALL_AS_USER=yes to my port's MAKE_ENV and
> > BUILD_ENV, and that did not appear to have any effect.
>
> First, let me say that a port should really not use the base system
> bsd.prog.mk bsd.lib.mk, and such, because they are moving targets, and
> can break your port in no time.
>
> Now, you need to remove all user/groups from the software's Makefile so
> that it does not try to chown/grp things, and you must put all the
> user/group things in the pkg-plist file using @owner and @group.
>
> --
> Mathieu Arnold
>
>
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Galera

[Walter Schwarzenfeld]

Try:
Comment out in
textproc/py-cloud_sptheme/Makefile
PYDISTUTILS_BUILDARGS= build_sphinx -E
@${MKDIR} ${STAGEDIR}${DOCSDIR} ${STAGEDIR}${DOCSDIR2}
${INSTALL_DATA} ${DOC_FILES1:S|^|${DOCSRCDIR1}/|} ${STAGEDIR}${DOCSDIR}
${INSTALL_DATA} ${DOC_FILES2:S|^|${DOCSRCDIR2}/|} ${STAGEDIR}${DOCSDIR2}
@${MKDIR} ${STAGEDIR}${DOCSDIR3} ${STAGEDIR}${DOCSDIR4}
${INSTALL_DATA} ${DOC_FILES3:S|^|${DOCSRCDIR3}/|} ${STAGEDIR}${DOCSDIR3}
${INSTALL_DATA} ${DOC_FILES4:S|^|${DOCSRCDIR4}/|} ${STAGEDIR}${DOCSDIR4}

(thes are only DOCS)

and in galera
USE_GCC=   yes
(has also an compile errot).

but so it compiles and installs (I hope it will work correctly).
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Galera

[Walter Schwarzenfeld]

Forgot:
Either you comment out broken in py-cloud_sptheme Makefile or you have 
compile it with make TRYBROKEN=yes.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Galera

[Walter Schwarzenfeld]

I correct this (there are too much warnings)
for Galera:
let USE_GCC in the Makefile
and use from commandline
make CC=/usr/local/bin/gcc49 CXX=/usr/local/bin/g++49 
CPP=/usr/local/bin/cpp49


(in the moment I don't find a working Syntax for the Makefie).

But so there are no warnings.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Galera

[Walter Schwarzenfeld]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212492
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Galera

[Walter Schwarzenfeld]

There is a patch, unbreaks py-cloud_sptheme.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Using bsd.prog.mk in source Makefile

[Mathieu Arnold]

Le 08/09/2016 à 18:00, Reid Linnemann a écrit :
> I really don't want to use autotools for this project, as it is only
> for a freebsd product, and bsd.prog.mk  and
> bsd.lib.mk  make things very easy, especially when
> I want to build and install the project outside of the context of a
> port. What alternatives would you suggest? Others in my group have
> overridden the do-install port target to avoid invoking the source
> install target, but I think that's a little kludgey.
>

I would suggest creating a simple Makefile manually.

-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: Galera

[Walter Schwarzenfeld]

Sorry, forgot the link:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212496
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ${INSTALL_DATA} problems

[Aristedes Maniatis]

Thanks Mathieu

On 8/09/2016 10:47pm, Mathieu Arnold wrote:
> Like Matthew said, INSTALL_DATA is for installing one file, not a
> directory hierarchy, this is done using COPYTREE_SHARE. As a side not,
> we never use CP -R to install files.

I'm trying to do my best to follow the rules, but the rules are very hard to 
find. For example if the docs mentioned the one file thing for INSTALL_DATA 
that would be helpful. Or if the error message was clear... I also don't 
understand the need for a recursive COPYTREE_SHARE which I believe requires a 
"cd" first, and a non-recursive INSTALL_*. Maybe the Makefile language will 
become clearer to me one day, but I've been using FreeBSD since 4.0 and it 
hasn't clicked yet.

 
> Now, I'm seeing something else that is a bad idea, it is using the -o
> flag.  Ports must build as a regular user.  A regular user will not be
> able to change the owner of the files.

Then why does INSTALL_DATA have an -o flag at all? I copied this idea from 
another port I found.

>  This must be done in the
> pkg-plist file, using @owner/@group as described in the Porter's
> Handbook:
> https://www.freebsd.org/doc/en/books/porters-handbook/plist-keywords.html

OK, thanks. I appreciate your help and I'll try your suggestions.


Ari



-- 
-->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

GeForce GTX 750 Ti upgraded to unsupported

[Russell L. Carter]

Greetings,

Since I upgraded to 11/stable from 10/stable, it appears that my video
card is no longer supported by either nvidia-driver or nvidia-driver-340:

 77.208] (WW) NV: Ignoring unsupported device 0x10de1380 (GM107 
[GeForce GTX 750 Ti]) at 01@00:00:0


The error message is identical for either.  Either port provides
graphics via the VESA driver.

However, a typical error is:

rcarter@feyerabend> firefox
Xlib:  extension "GLX" missing on display ":0"

Any ideas?

Thanks,
Russell

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ${INSTALL_DATA} problems

[Mark Linimon]

On Fri, Sep 09, 2016 at 08:29:12AM +1000, Aristedes Maniatis wrote:
> Maybe the Makefile language will become clearer to me one day, but
> I've been using FreeBSD since 4.0 and it hasn't clicked yet.

Don't worry, the FreeBSD ports framework does things with the Makefile
language that was never intended by make's designers :-)

We do try to document things in the Porter's Handbook, but sometimes
the only thing to do is wade into bsd.port.mk and friends and read the
code.  (Not recomended for the faint of heart, though.)

mcl
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: GeForce GTX 750 Ti upgraded to unsupported

[Ben Woods]

On Friday, 9 September 2016, Russell L. Carter  wrote:

> Greetings,
>
> Since I upgraded to 11/stable from 10/stable, it appears that my video
> card is no longer supported by either nvidia-driver or nvidia-driver-340:
>
>  77.208] (WW) NV: Ignoring unsupported device 0x10de1380 (GM107 [GeForce
> GTX 750 Ti]) at 01@00:00:0
>
> The error message is identical for either.  Either port provides
> graphics via the VESA driver.
>
> However, a typical error is:
>
> rcarter@feyerabend> firefox
> Xlib:  extension "GLX" missing on display ":0"
>
> Any ideas?
>
> Thanks,
> Russell
>

Just a guess, you haven't been bitten by the recent update that is
associated with this UPDATING entry have you?

 https://svnweb.freebsd.org/ports/head/UPDATING?r1=421096&r2=421117

Regards,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ${INSTALL_DATA} problems

[Aristedes Maniatis]

On 9/09/2016 9:13am, Mark Linimon wrote:
> On Fri, Sep 09, 2016 at 08:29:12AM +1000, Aristedes Maniatis wrote:
>> Maybe the Makefile language will become clearer to me one day, but
>> I've been using FreeBSD since 4.0 and it hasn't clicked yet.
> 
> Don't worry, the FreeBSD ports framework does things with the Makefile
> language that was never intended by make's designers :-)
> 
> We do try to document things in the Porter's Handbook, but sometimes
> the only thing to do is wade into bsd.port.mk and friends and read the
> code.  (Not recomended for the faint of heart, though.)

I think the most useful thing that could be done is more examples. Even a list 
of ports which implement things in the recommended ways and do the full range 
of common things.

/var/poudriere/ports/default # grep -R {CP} * | wc -l
1504

So me copying how mariadb101 does it (for example), gives me the wrong result. 
If I had a dozen "best practices" Makefiles I could copy them.


The second most useful thing would be to enhance portlint. Right now it feels 
like 95% of what it does is enforce some arbitrary ordering of keywords. But if 
it instead gave you hints "I see you are using {INSTALL_DATA} with a wildcard 
or directory, instead you should use {COPYTREE_SHARE}" then much time would be 
saved.


Cheers
Ari





-- 
-->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Galera

[Walter Schwarzenfeld]

p27-cloud_sptheme is fixed and comitted.
For galera there is another PR. Seem there exists more problems.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208109
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"